CN110717123A - Page response method and device, electronic equipment and storage medium - Google Patents
Page response method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN110717123A CN110717123A CN201910944414.2A CN201910944414A CN110717123A CN 110717123 A CN110717123 A CN 110717123A CN 201910944414 A CN201910944414 A CN 201910944414A CN 110717123 A CN110717123 A CN 110717123A
- Authority
- CN
- China
- Prior art keywords
- page
- parent
- child
- sub
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the disclosure discloses a page response method, a page response device, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a search request of a sub-page search sub-page service; searching whether the child page service exists in a child scope container of the child page according to the search request, wherein the child scope container is established in a parent scope container in a parent page, and the life cycle of a storage space of the parent scope container is longer than that of a page workflow; the parent page comprises the child page; and if the sub-page service exists in the sub-scope container, returning to the sub-page service. The technical scheme of the embodiment of the disclosure solves the technical problems that resource occupation and resource waste are caused when the page workflow continues to access the same page when the page workflow is destroyed in the existing page response method, and even the page response speed is low, so that the resource configuration is optimized, the page response speed is increased, and the technical effect of user experience is improved.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, and in particular relates to a page response method and device, an electronic device and a storage medium.
Background
The smart phone and the wireless network not only solve the problem of two-party or multi-party communication, but also provide more choices for the learning, working, entertainment and the like of the user. For example, various clients are installed on a mobile phone to watch videos and the like. The development of the existing client pays more and more attention to user experience, so that the optimization of the response speed of the client is also one of the key research and development directions of client developers.
In order to provide diversified page services, it is common to include sub-pages in a page, and even still include sub-pages in sub-pages. For such a page having a parent-child relationship, in the process of responding to a child page service, the service of the child page to be provided is usually directly stored in the parent page, and then an additional disclosure method, for example, a disclosure call interface API, is provided. When a child page needs to call the service of the child page, the service of the child page provided by a parent page is called by calling the public method.
However, the current processing method causes the problems of resource waste and excessively slow response speed in some special scenes.
Disclosure of Invention
The embodiment of the disclosure provides a page response method, a page response device, an electronic device and a storage medium, so as to solve the technical problems that when a page workflow is destroyed in the existing page response method, continuous access to the same page causes resource waste and slow page response speed in some special scenes, and achieve the technical effects of improving the page response speed and improving user experience.
In a first aspect, an embodiment of the present disclosure provides a page response method, where the method includes:
receiving a search request of a sub-page search sub-page service;
searching whether the child page service exists in a child scope container of the child page according to the search request, wherein the child scope container is established in a parent scope container in a parent page, and the life cycle of a storage space of the parent scope container is longer than that of a page workflow; the parent page comprises the child page;
and if the sub-page service exists in the sub-scope container, returning to the sub-page service.
In a second aspect, an embodiment of the present disclosure further provides a page response apparatus, where the apparatus includes:
the search request receiving module is used for receiving a search request of the sub-page search sub-page service;
a child page service obtaining module, configured to find whether the child page service exists in a child scope container of the child page according to the search request, where the child scope container is created in a parent scope container in a parent page, and a life cycle of a storage space of the parent scope container is longer than a life cycle of a page workflow; the parent page comprises the child page;
and the sub-page service returning module is used for returning the sub-page service if the sub-page service exists in the sub-scope container.
In a third aspect, an embodiment of the present disclosure further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a page response method as in any of the embodiments of the present disclosure.
In a fourth aspect, the disclosed embodiments also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the page response method according to any one of the disclosed embodiments.
The technical scheme of the embodiment of the disclosure is that a sub-scope container is created in a parent scope container in a parent page, and the parent scope container is stored in a storage space with a life cycle longer than that of a page workflow, which is different from the prior art that the page service is stored in the page workflow, so that the page service stored in the sub-scope container and the parent scope container can be retained, that is, even if the page workflow is rebuilt after being rebuilt, when a search request for searching the sub-page service by the sub-page is received, the sub-page service can be searched in the sub-scope container as before the page workflow is destroyed, if the sub-page service exists in the sub-scope container, the sub-page service is returned, and the problem that in the prior art, when the page workflow is destroyed, if the same sub-page is to be continuously visited, the sub-page service needs to be reloaded is solved, resource occupation is caused, resource waste is caused, even the technical problem that the response speed of the sub-page is low is solved, the resource configuration is optimized, the page response speed is improved, and the technical effect of user experience is improved.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
Fig. 1 is a schematic flow chart of a page response method according to a first embodiment of the disclosure;
fig. 2 is another schematic flow chart of a page response method according to a second embodiment of the disclosure;
fig. 3 is a schematic diagram of a corresponding relationship between a page and a page scope according to a second embodiment of the disclosure;
fig. 4 is another schematic flow chart of a page response method according to a third embodiment of the disclosure;
fig. 5 is a schematic structural diagram of a page response apparatus according to a fourth embodiment of the disclosure;
fig. 6 is a schematic structural diagram of an electronic device according to a fifth embodiment of the disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
Example one
Fig. 1 is a schematic flow chart of a page response method provided by an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a situation where a user calls a desired page service based on an original manner when rebuilding a page before rotation, and the method may be executed by a page response apparatus, and the apparatus may be implemented in a form of software and/or hardware, and optionally, implemented by an electronic device, and the electronic device may be a mobile terminal, a PC terminal, and the like.
As shown in fig. 1, the method of this embodiment includes:
s110, receiving a search request of the sub-page search sub-page service.
Here, the entire frame corresponding to the entire page may be referred to as a root page. If at least one space is provided on one page for placing another page, the page placed on the at least one space may be referred to as a child page, and the page accommodating the child page may be referred to as a parent page. It will also be appreciated that at least two controls are included on a parent page, each control for placing a page, with the page placed on each control as a child page. That is, pages nested on a parent page are child pages. And taking the functions or services which can be realized by the sub-page as the sub-page service corresponding to the sub-page. It will be appreciated that the root page is also the parent page of the pages nested on the root page.
In the embodiment of the present disclosure, the search request may refer to a request for obtaining a page service of a certain sub-page. The search request may carry a page service identifier corresponding to the page service. Specifically, when a user triggers a control on a sub-page, that is, when a request for searching for a page service is sent to a server, a server may receive the page service search request and determine a page service identifier carried in the search request.
Illustratively, one parent page includes five sub-pages, sub-page a, sub-page B, sub-page C, sub-page D, and sub-page E. When a user triggers the sub-page A, namely the page service corresponding to the sub-page A is obtained, the server receives a page service searching request for obtaining the sub-page A.
It should be noted that, if there is no other nested page in the sub-page a, the server receives a sub-page service responding to the sub-page a, and if there is another nested page in the sub-page a, the search request received by the server may be a page service responding to the sub-page a, or may be a page service corresponding to another page nested in the sub-page a.
S120, whether the sub-scope service exists in the sub-scope container of the sub-page is searched according to the searching request.
The child scope container is established in a parent scope container in a parent page, and the life cycle of the storage space of the parent scope container is longer than that of the page workflow; the parent page includes child pages.
In particular, the lifecycle of a page workflow may understand the process of a page from generation to destruction. Illustratively, the lifecycle of a page workflow may include the stages of initializing, creating a view, visible (display), invisible (hide), destroying a view, and destroying a page.
In the embodiment of the present disclosure, a container storing page services corresponding to respective pages is taken as a scope container. The scope container corresponding to the parent page is called as a parent scope container; the scope container corresponding to a sub-page is referred to as a sub-scope container. Taking the page service stored in the parent scope container as a parent page service; and the page service stored in the sub-scope is used as the sub-page service. Because the nested relation exists between the parent page service and the child page service, the parent scope container corresponding to the parent page can be established first, and each child scope container can be established in the parent scope container. That is, the scope range of the parent scope container is larger than the scope range of the child scope container.
In the prior art, because some operations executed by a user when accessing a page may require destroying an existing page workflow and recreating the page workflow, the service stored in the parent page workflow is destroyed, and the user cannot call the service of a required child page through an original public method. If the user needs to continue to view the child page after the page workflow is destroyed, the service required by the child page needs to be restored in the newly created parent page workflow, which may cause resource occupation and resource waste to a certain extent. Moreover, when the service required by the sub-page involves a service parameter that changes due to the running of the page, the page operation before the screen rotation needs to be repeatedly executed, which may slow down the response speed of the sub-page and affect the user experience.
In view of the above drawbacks, the embodiment of the present disclosure creates a sub-scope container in a parent page, and further stores the page service of the sub-page service in the sub-scope container corresponding to the sub-page or the parent scope container of an upper parent page of the sub-page, and ensures that the life cycle of the storage space of the parent scope container is longer than the life cycle of the page workflow, so that it can be ensured that the parent scope container is not destroyed when the page workflow is destroyed, and because the sub-scope container creates the parent scope container, and further ensures that the sub-scope container is not destroyed, the page service of the sub-page in the sub-scope container or the parent scope container is also saved, so that when the user continues to view the sub-page after the page workflow is destroyed and reconstructed, it is only necessary to continue to search the required sub-page service from the sub-scope container of the sub-page according to the search request, the sub-page service does not need to be reloaded, and the problems of repeated occupation of resources and resource waste are avoided.
Illustratively, the parent scope container may be hosted in a reservation Fragment Retain Fragment, or the parent scope container may be deposited in memory based on static variables. Because the retention Fragment Retain Fragment and the static parameters in the memory have the functions of saving and restoring, and the life cycle of the retention Fragment Retain Fragment and the static parameters in the memory is longer than that of the page workflow, the parent scope container is hosted in the static parameters in the retention Fragment memory, and can store each scope container. It is understood that the target page may be a parent page or a child page.
Specifically, when a search request is received, the page service corresponding to the page service identifier can be searched from the sub-scope container corresponding to the sub-page according to the page service identifier in the search request.
Of course, in the process of actual application, when the user triggers the operation and the server receives the search request corresponding to the trigger operation, the page service corresponding to the trigger operation may be determined, that is, when responding to the page, the page service does not need to be searched according to the page service identifier, and the specific search details of the page service are not specifically limited herein.
Illustratively, when the received lookup request is: and acquiring the sub-page service corresponding to the sub-page A, and searching whether the page service corresponding to the page service identifier exists in the sub-scope container A' corresponding to the sub-page A by the server according to the page service identifier in the search request.
S130, if the sub-page service exists in the sub-scope container, returning the sub-page service.
Specifically, if the sub-page service corresponding to the page service identifier is obtained from the sub-scope container according to the page service identifier in the search request, the sub-page service is returned.
Of course, in the process of actual application, there is a page service required by all the child pages as a certain page service, and such a page service can be stored in the parent scope container. If the search request needs to acquire such a page service, the page service cannot be acquired from the corresponding sub-scope container, that is, the response to the page cannot be realized.
Optionally, if the child scope container does not have the child page service, finding a parent scope container of a parent page of the child page; if the child page service exists in the parent scope container, the child page service is returned.
Specifically, when the child page service is not found from the child scope corresponding to the child page, it may be searched upstream whether the child page service is stored in the parent scope container including the child scope container. If the child page service is stored in the parent scope container, the found child page service is returned, namely, the triggering operation of the user is responded, for example, the required page service slides left and right, and when the child page service is found, the page slides left and right.
Optionally, if the child page service does not exist in the parent scope container, the parent scope container is used as a new child scope container, the operation of searching for the parent scope container of the parent page of the child page is repeatedly executed, and the search result is returned. For example, a page may be recursively looked up through getScope (). getservice (object) to serve children pages stored in the parent scope container of the parent page.
It should be noted that one parent page 1 may include at least one child page A, B, C, and if at least one child page a11 and a12 is also nested in the child page a, at this time, the child page a may be used as a parent page of the child page a11 and a12, and child scope containers corresponding to the respective child pages are sequentially created in the parent scope container. If each scope container is introduced through the tree diagram, the parent scope container corresponding to the parent page may be used as a root node, the child scope container corresponding to each child page may be used as a leaf node, and if the child page further includes other child pages, the leaf node may be used as the root node, and the child scope container corresponding to other child pages may be used as the leaf node.
It can be understood that if the child page service is not included in the parent scope, the parent scope is taken as a new child scope, the child page service exists in the parent scope including the new child scope is searched in an uplink mode, and by analogy, whether the page service exists in each scope container is searched in an uplink mode, and the searched result is returned.
Wherein, the search result can include two cases. Optionally, the search result includes the found sub-page service, and then the sub-page service is returned to respond to the search request. In addition, there may be a case where the child page service cannot be found, that is, the child page service is not found in the scope container corresponding to the root page, and at this time, an empty message may be generated, that is, an empty message may be generated when the child page service is not found in the parent scope container of the parent page at the uppermost layer. Of course, the prompt information that the sub-page service cannot be obtained can also be generated, and the prompt information is returned for the user to view.
In the technical scheme of this embodiment, a child scope container is created in a parent scope container in a parent page, and the parent scope container is stored in a storage space with a lifetime longer than that of a page workflow, which is different from a mode of storing a page service in a page workflow in the prior art, so that the page service stored in the child scope container and the parent scope container can be retained, that is, even if the page workflow is destroyed and reconstructed, when a search request for searching the child page service from the child page is received, the child page service can be searched in the child scope container as before the page workflow is destroyed, if the child page service exists in the child scope container, the child page service is returned, thereby solving the problem that in the prior art, if the same child page is to be continuously accessed, the child page service needs to be reloaded, resource occupation is caused, resource waste is caused, even the technical problem that the response speed of the sub-page is low is solved, the resource configuration is optimized, the page response speed is improved, and the technical effect of user experience is improved.
Example two
On the basis of the technical scheme, before receiving the operation of the sub-page service, the scope container corresponding to the parent page and the sub-page also needs to be created. Fig. 2 is another schematic flow chart of a page response method according to a second embodiment of the disclosure.
As shown in fig. 2, the method includes:
s210, when a parent page is generated, a parent scope container is created, and a parent page service and a child page service are stored in the parent scope container; wherein the parent page includes at least one child page.
Where the newly created page may be taken as the parent page. At least one space for placing pages can be set on the parent page, and the pages placed on the spaces are used as child pages. Optionally, the number of the sub-pages on the parent page may be one, two or more, and the number of the sub-pages may be determined according to actual situations. If at least one space is set on the sub-page for placing the page, that is, the sub-page is nested in the sub-page, the sub-page can be used as a parent page, and each page nested on the sub-page is used as a sub-page. Accordingly, in order to store the page services corresponding to the respective pages, when the parent page is created, a parent scope container corresponding to the parent page may be created at the same time, and the parent scope container may store the parent page service and the page services common to all the child pages.
Optionally, in order to quickly invoke the page service corresponding to the child page, the child page is established in the parent page, and meanwhile, the child scope container storing the page service corresponding to each child page is established in the parent scope container.
Illustratively, referring to fig. 3 (a), page 1 is created, page 1 is taken as a parent page, three spaces are provided on the parent page, and pages placed on the three spaces are taken as child pages, which may be respectively referred to as child page a, child page B, and child page C. If three pages are also nested in the sub-page A, marking the page as A11、A12、A13That is, the sub-page A can be regarded as the page A11、A12、A13Of the parent page, page A11、A12、A13Is a child page of the parent page a. Wherein, at least one page is also nested in the sub-page B and respectively marked as B11、B12…, non-nested pages in C page. Then the parent scope container corresponding to each parent page and the child scope container corresponding to the child page are established, as shown in fig. 3 (b). And establishing a parent scope container corresponding to the parent page 1, and recording the parent scope container as 1' for storing the page service corresponding to the parent page 1 and/or storing the page services common to the child page A, the child page B and the child page C. After the father scope container is established, respectively establishing child scope containers A ', B' and C 'corresponding to the child page A, the child page B and the child page C, and respectively storing the child scope containers A', B 'and C' to the page service corresponding to the child page A, the page service of the child page B and the page service of the child page C. It should be noted that, at least one page a is also nested in the sub-page a11、A12、A13Therefore, it is also necessary to establish page A separately11、A12、A13Corresponding scope Container A11’、A12’、A13'. The sub scope container corresponding to page A is used as scope container A11’、A12’、A13The parent scope container of' and so on, when pages are nested in a page, this way can be used to determine the scope container corresponding to each page. In the same wayAnd taking the child page B as a parent page, and establishing scope containers which are nested in the parent page B and correspond to the child pages.
In this embodiment, it is optional to store the page service specific to each page in the scope container corresponding to each page, and store the page service common to all the child pages in the parent scope container, so that the following advantages are provided: when the page service is obtained, the corresponding page service can be searched step by step, so that the efficiency of searching the page service is improved, and the problem of redundancy of the scope container caused by storing all the page services to one scope container is solved.
S220, when the child page is added to the parent page, creating a child scope container in the parent scope container of the parent page.
It will be appreciated that a space is newly set in the parent page for placing a new page, and the newly placed page at this time is taken as a child page added in the parent page. Correspondingly, when a child page is added in a parent page, a scope container corresponding to the newly added child page is established in the parent scope container of the parent page.
Illustratively, referring to (C) and (D) in fig. 3, when a child page D is added in the parent page 1, a child scope container D' corresponding to the child page D is created in the parent scope container. If page D is added to the sub-page D11The child page D is taken as the parent page of the child page D11. Accordingly, the sub-page D also needs to be established11That is, the sub-scope container corresponding to the sub-page D is used as the sub-scope container D11The parent scope container of (2).
S230, when the page workflow is detected to be destroyed, acquiring the parent page loaded before the page workflow is destroyed, and storing the parent scope container corresponding to the parent page and the child scope container of the child page of the parent page.
Alternatively, whether or not a situation in which the page workflow is destroyed occurs may be determined by whether or not a preset operation is received. Illustratively, when the screen is detected to rotate, it may be determined that the page workflow is detected to be destroyed; alternatively, when it is detected that the language type is switched, it may be determined that the page workflow is detected to be destroyed; still alternatively, when a change in the terminal keyboard display mode or the input mode is detected, it may be determined that the page workflow is detected to be destroyed, and the like. It is to be understood that the above operation manner is only used for an exemplary illustration of a scenario in which the page workflow is destroyed in the embodiment of the present disclosure, and is not a limitation to the scenario in which the page workflow is destroyed in the present disclosure, and besides the scenario, other situations that may cause the workflow to be destroyed may also be included. For example, when it is detected that the vertical screen display is switched to the horizontal screen display, specifically, the page displayed by the vertical screen display is destroyed, that is, the existing page is destroyed when the screen rotates, and the horizontal screen display page corresponding to the page before the page is not rotated is created again. For fast page re-creation, the parent page loaded before screen rotation may be acquired. And simultaneously saving a parent scope container corresponding to the parent page and scope containers of all sub-pages of the parent page so as to call page services corresponding to all the sub-pages stored in the parent scope container or the sub-scope containers.
S240, receiving a search request of the sub-page search sub-page service.
Specifically, when the user triggers a control corresponding to the acquisition of a certain page service on the page, optionally, when triggering the operation of acquiring a sub-page service corresponding to the sub-page a, the server may receive a search request for searching the sub-page service.
And S250, searching whether the sub-scope service exists in the sub-scope container of the sub-page according to the searching request.
Specifically, according to the service identifier in the search request, whether the page service exists in the sub-scope container corresponding to the service identifier may be first searched, and if the sub-page service corresponding to the user trigger operation is not found, whether the sub-page service corresponding to the user trigger operation exists is searched in an uplink manner, that is, whether the sub-page service exists in an upper parent scope container of the sub-scope container is searched. If the sub-page service exists, returning the sub-page service, if the sub-page service does not exist, sequentially searching whether the sub-page service exists or not in an uplink mode, and if the sub-page service is not searched after all scope containers are traversed, returning to be null, namely no response exists.
Illustratively, if the trigger is to obtain the sub-page A11When the sub-page of S is used for searching the request, the sub-page A can be searched first11Relative sub-scope containers A11' find if there is a stored sub-page service S. If yes, returning the sub-page service S; if not, sequentially searching the containers A including the sub-scope in an ascending way11If the child page service S exists in the parent scope container A', returning the child page service S; otherwise, continuously searching the parent scope container 1 'including the child scope container A' in an uplink manner to determine whether the child page service S exists, if so, returning the child page service S, otherwise, returning to the null state, namely, no response exists.
And S260, if the sub-page service exists in the sub-scope container, returning the sub-page service.
That is, when the sub-page service is found from the sub-scope container according to the search request, the sub-page service is returned.
According to the technical scheme, the page service corresponding to the sub-page is stored in the storage space with the life cycle longer than that of the page workflow, when the page workflow is destroyed, the parent page loaded by the destroyed page workflow is obtained, and the parent scope container corresponding to the parent page and the sub-scope container of the sub-page of the parent page are stored, so that the corresponding page service can be obtained no matter whether the page is rebuilt or not, and the page response speed and the technical effect of user experience are improved.
EXAMPLE III
As a preferred embodiment of the foregoing embodiment, fig. 4 is another schematic flow chart of a page response method provided in a third embodiment of the present disclosure.
As shown in fig. 4, the method includes:
and S410, the sub-page needs sub-page service.
This exampleSpecific examples are given as examples. The parent page 1 is provided with three spaces for placing the child page a, the child page B, and the child page C, that is, the parent page 1 includes three child pages A, B, C. The page services corresponding to the sub-page A, B, C, respectively, may be stored to their corresponding sub-scope containers A ', B ', C '. Storing the page service corresponding to the sub-page A into a sub-scope container A', optionally, storing the sub-page service A in the sub-scope container1、A2、A3In this manner, the page services corresponding to each sub-page are stored in the corresponding sub-scope container. The page service that also contains the child page A, B, C can be stored in the parent scope container 1 'corresponding to the parent page 1, e.g., the page service S that also contains the child page A, B, C is placed in the parent scope container 1'.
Specifically, when the user triggers the control corresponding to the sub-page, that is, the sub-page service corresponding to the sub-page is triggered to be acquired, the request information for acquiring the sub-page service may be sent to the server.
Illustratively, when the user triggers the sub-page A, the sub-page service A is acquired1When corresponding operation is performed, the acquired page service A is sent to the server1The server may receive the get page service A1The request information of (1).
S420, judging whether the sub-scope container corresponding to the sub-page has sub-page service, if so, executing S450; if not, go to S430.
After the server receives the request information for acquiring the sub-page service, it can search whether the sub-page service corresponding to the request information is stored or not from the sub-scope container corresponding to the sub-page.
Specifically, the sub-page service corresponding to the page service identifier may be searched from the corresponding sub-scope container according to the page service identifier corresponding to the sub-page service carried in the request information. If the page service corresponding to the service identifier exists in the sub-scope container, executing S450; if the page service corresponding to the service identifier does not exist in the sub-scope container, S430 is executed.
Illustratively, the server receives the get pages service A1Can confirm the existence of A from the sub-scope container A' corresponding to the sub-page A1Page service of (2), at which time page service A can be served1Returning, S450 is executed. If the server receives the request information for obtaining the page service S, it may first search whether the sub-scope container a' corresponding to the sub-page a has the page service S, and if not, execute S430.
S430, searching the child page service from the parent scope container corresponding to the parent page.
That is, when the sub-page service corresponding to the request information is not found from the sub-scope container, the sub-page service corresponding to the request information may be found from the parent scope container including the sub-scope container.
For example, when the server receives the request information for obtaining the page service S, it may first search whether the page service S exists in the sub-scope container a' corresponding to the sub-page a. If not, the child page service S may be looked up from the parent scope container 1, which includes the child scope container A'.
S440, judging whether the child page service exists in the parent scope container, if so, executing S450; if not, go to S460.
And searching whether a sub-page service corresponding to the page service identifier exists in the parent scope container according to the service identifier carried in the request information. If so, return to the sub-page service, i.e., execute S450, and if not, return to null, i.e., execute S460.
Illustratively, when the server searches the page service S from the parent scope container 1 according to the request information for obtaining the page service S, the server returns to the page service S; and if the server does not find the sub-page service S from the parent scope container according to the request information for obtaining the page service S', returning to be null.
S450, directly returning to the sub-page service.
It can be understood that the sub-page service is returned after the sub-page service corresponding to the request information is acquired.
And S460, returning to be null.
It can be understood that if all the child scope containers and the parent scope container are traversed in a manner of recursively searching from the child scope container to the parent scope container, and the child page service corresponding to the request information is not acquired yet, the return is null.
It should be noted that, in this embodiment, the case that the parent page includes at least one child page is used, but the case that the child page is still nested in the child page is not included, but the case that other child pages are still nested in the child page is also applicable, and by using the technical solution of this embodiment, whether the required child page service exists in the parent scope container corresponding to the parent page is sequentially searched until the child page service is returned, or the child page service is returned to null.
According to the technical scheme of the embodiment, a Scope container is created for each page, the Scope container is hosted in the reserved Fragment Rmail Fragment, because the life cycle of the Rmail Fragment is longer than that of the page workflow, the Scope container is not influenced by the Activity of the page workflow caused by screen rotation, when a search request of searching the child page service for the child page is received, whether the child page service exists in the child Scope container of the child page or the parent Scope container of the child page is searched up step by step according to the search request, if the child page service exists, the child page service is returned, the problem that in the prior art, page services corresponding to the parent page and the child page are all stored on the parent page is solved, when the page workflow is executed, the page service destroying connection belt stored on the workflow is destroyed, and if a user needs to continue to check the child page after rotating the screen, the service required by the sub-page needs to be stored in the re-created page workflow, that is, the page operation before the page workflow is destroyed is repeatedly executed, so that the technical problems of resource occupation and resource waste, even slow response speed of the sub-page are caused, and the corresponding page service can be obtained regardless of whether the page workflow is reconstructed, so that the resource waste is avoided, the page response speed is improved, and the technical effect of user experience is improved.
Example four
Fig. 5 is a schematic structural diagram of a page response apparatus according to a fourth embodiment of the disclosure, and as shown in fig. 5, the apparatus includes: a search request receiving module 510, a sub-page service obtaining module 520, and a sub-page service returning module 530.
A search request receiving module 510, configured to receive a search request for a sub-page search sub-page service; a sub-page service obtaining module 520, configured to find whether the sub-page service exists in a sub-scope container of the sub-page according to the search request, where the sub-scope container is created in a parent scope container in a parent page, and a life cycle of a storage space of the parent scope container is longer than a life cycle of a page workflow; the parent page comprises the child page; a sub-page service returning module 530, configured to return the sub-page service if the sub-page service exists in the sub-scope container.
The technical scheme of the embodiment of the disclosure is that a sub-scope container is created in a parent scope container in a parent page, and the parent scope container is stored in a storage space with a life cycle longer than that of a page workflow, which is different from the prior art that the page service is stored in the page workflow, so that the page service stored in the sub-scope container and the parent scope container can be retained, that is, even if the page workflow is rebuilt after being rebuilt, when a search request for searching the sub-page service by the sub-page is received, the sub-page service can be searched in the sub-scope container as before the page workflow is destroyed, if the sub-page service exists in the sub-scope container, the sub-page service is returned, and the problem that in the prior art, when the page workflow is destroyed, if the same sub-page is to be continuously visited, the sub-page service needs to be reloaded is solved, resource occupation is caused, resource waste is caused, even the technical problem that the response speed of the sub-page is low is solved, the resource configuration is optimized, the page response speed is improved, and the technical effect of user experience is improved.
On the basis of the above technical solutions, the apparatus further includes: a scope lookup module comprising:
a first searching unit, configured to search a parent scope container of a parent page of the child page if the child page service does not exist in the child scope container;
and the second searching unit is used for returning the child page service if the child page service exists in the parent scope container.
On the basis of the above technical solutions, the apparatus further includes: a third searching unit for:
if the child page service does not exist in the parent scope container, the parent scope container is used as a new child scope container, the operation of searching the parent scope container of the parent page of the child page is repeatedly executed, and the search result is returned. On the basis of the above technical solutions, before receiving the operation of searching the sub-page service by the sub-page,
the scope container establishing module is used for establishing a parent scope container when a parent page is generated, and storing a parent page service and a child page service in the parent scope container; wherein the parent page comprises at least one child page.
And the scope adding module is used for creating a child scope container in the parent scope container of the parent page when the child page is added in the parent page.
On the basis of the above technical solutions, the scope adding module includes:
and the child service storage unit is used for storing a parent page service and at least one hierarchy of child page services of the parent page in the parent scope container.
On the basis of the foregoing technical solutions, the search request receiving module, before receiving a search request of a sub-page search sub-page service, is further configured to:
when the fact that the page workflow is destroyed is detected, the parent page loaded before the page workflow is destroyed is obtained, and a parent scope container corresponding to the parent page and a child scope container of a child page of the parent page are saved.
The page response device provided by the embodiment of the disclosure can execute the page response method provided by any embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the embodiments of the present disclosure.
EXAMPLE five
Referring now to fig. 6, a schematic diagram of an electronic device (e.g., the terminal device or the server in fig. 6) 600 suitable for implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from storage 606 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 606 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network through the communication device 609, or installed from the storage device 606, or installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
The electronic device provided by the embodiment of the disclosure and the page response method provided by the embodiment belong to the same inventive concept, and technical details that are not described in detail in the embodiment can be referred to the embodiment, and the embodiment have the same beneficial effects.
EXAMPLE six
The disclosed embodiments provide a computer storage medium on which a computer program is stored, which when executed by a processor implements the page response method provided by the above embodiments.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText transfer protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a search request of a sub-page search sub-page service; searching whether the child scope service exists in a child scope container of the child page according to the search request, wherein the child scope container is established in a parent scope container in a parent page, and the life cycle of the storage space of the parent scope container is longer than that of a page workflow; the parent page comprises the child page; and if the sub-page service exists in the sub-scope container, returning to the sub-page service.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation on the unit itself, for example, a sub-service deposit unit may also be described as a "sub-page service storage unit".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments of the present disclosure, [ example one ] there is provided a page response method, the method comprising:
receiving a search request of a sub-page search sub-page service;
searching whether the child page service exists in a child scope container of the child page according to the search request, wherein the child scope container is established in a parent scope container in a parent page, and the life cycle of a storage space of the parent scope container is longer than that of a page workflow; the parent page comprises the child page;
and if the sub-page service exists in the sub-scope container, returning to the sub-page service.
According to one or more embodiments of the present disclosure, [ example two ] there is provided a page response method, further comprising:
optionally, if the child scope container does not have the child page service, finding a parent scope container of a parent page of the child page;
and if the child page service exists in the parent scope container, returning to the child page service.
According to one or more embodiments of the present disclosure, [ example three ] there is provided a page response method, further comprising:
optionally, if the child page service does not exist in the parent scope container, the parent scope container is used as a new child scope container, the operation of searching for the parent scope container of the parent page of the child page is repeatedly executed, and a search result is returned.
According to one or more embodiments of the present disclosure, [ example four ] there is provided a page response method, further comprising:
optionally, the search result includes that the sub-page service is found, or an empty message is generated when the sub-page service is not found in the scope container corresponding to the root page.
According to one or more embodiments of the present disclosure, [ example five ] there is provided a page response method, further comprising:
optionally, before the operation of receiving the sub-page lookup sub-page service, the method further includes:
creating a parent scope container when a parent page is generated, and storing a parent page service and a child page service in the parent scope container; wherein the parent page comprises at least one child page.
When a child page is added to the parent page, a child scope container is created in the parent scope container of the parent page.
According to one or more embodiments of the present disclosure, [ example six ] there is provided a page response method, further comprising:
optionally, the storing the parent page service and the child page service in the parent scope container includes:
and storing a parent page service and at least one level of child page service of the parent page in the parent scope container.
According to one or more embodiments of the present disclosure, [ example seven ] there is provided a page response method, further comprising:
optionally, the storing, in the parent scope container, a parent page service and a child page service of at least one hierarchy of the parent page includes:
and storing a parent page service and a child page service of a first level of the parent page in the parent scope container.
According to one or more embodiments of the present disclosure, [ example eight ] there is provided a page response method, further comprising:
optionally, before the receiving a search request of a sub-page search sub-page service, the method further includes:
when the fact that the page workflow is destroyed is detected, the parent page loaded before the page workflow is destroyed is obtained, and a parent scope container corresponding to the parent page and a child scope container of a child page of the parent page are saved.
According to one or more embodiments of the present disclosure, [ example nine ] there is provided a page response apparatus including:
the search request receiving module is used for receiving a search request of the sub-page search sub-page service;
a child page service acquisition module, configured to search, according to the search request, whether the child scope container of the child page has the child page service, where the child scope container is created in a parent scope container in a parent page, and the parent scope container is hosted in a reserved fragment; the parent page comprises the child page;
and the sub-page service returning module is used for returning the sub-page service if the sub-page service exists in the sub-scope container.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (12)
1. A page response method, comprising:
receiving a search request of a sub-page search sub-page service;
searching whether the child page service exists in a child scope container of the child page according to the search request, wherein the child scope container is established in a parent scope container in a parent page, and the life cycle of a storage space of the parent scope container is longer than that of a page workflow; the parent page comprises the child page;
and if the sub-page service exists in the sub-scope container, returning to the sub-page service.
2. The method of claim 1, further comprising:
if the child scope container does not have the child page service, searching a parent scope container of a parent page of the child page;
and if the child page service exists in the parent scope container, returning to the child page service.
3. The method of claim 2, further comprising:
if the child page service does not exist in the parent scope container, taking the parent scope container as a new child scope container, repeatedly executing the operation of searching the parent scope container of the parent page of the child page, and returning a search result.
4. The method according to claim 3, wherein the search result comprises that the sub-page service is found, or an empty message is generated when the sub-page service is not found in the scope container corresponding to the root page.
5. The method of claim 1, prior to receiving the operation of the sub-page lookup sub-page service, further comprising:
creating a parent scope container when a parent page is generated, and storing a parent page service and a child page service in the parent scope container; wherein the parent page comprises at least one child page.
When a child page is added to the parent page, a child scope container is created in the parent scope container of the parent page.
6. The method of claim 1, wherein depositing a parent page service and a child page service in the parent scope container comprises:
and storing a parent page service and at least one level of child page service of the parent page in the parent scope container.
7. The method of claim 6, wherein storing the parent page service and at least one level of child page services of the parent page in the parent scope container comprises:
and storing a parent page service and a child page service of a first level of the parent page in the parent scope container.
8. The method of claim 1, prior to said receiving a search request for a sub-page search sub-page service, further comprising:
when the page workflow is destroyed, acquiring the parent page loaded before the page workflow is destroyed, and saving a parent scope container corresponding to the parent page and a child scope container of a child page of the parent page.
9. The method of claim 1, wherein the parent scope container is hosted in a reservation shard or wherein the parent scope container is deposited in memory based on a static variable.
10. A page response apparatus, comprising:
the search request receiving module is used for receiving a search request of the sub-page search sub-page service;
a child page service obtaining module, configured to find whether the child page service exists in a child scope container of the child page according to the search request, where the child scope container is created in a parent scope container in a parent page, and a life cycle of a storage space of the parent scope container is longer than a life cycle of a page workflow; the parent page comprises the child page;
and the sub-page service returning module is used for returning the sub-page service if the sub-page service exists in the sub-scope container.
11. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the page response method of any of claims 1-9.
12. A storage medium containing computer-executable instructions for performing the page response method of any one of claims 1-9 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910944414.2A CN110717123B (en) | 2019-09-30 | 2019-09-30 | Page response method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910944414.2A CN110717123B (en) | 2019-09-30 | 2019-09-30 | Page response method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110717123A true CN110717123A (en) | 2020-01-21 |
| CN110717123B CN110717123B (en) | 2022-04-22 |
Family
ID=69212144
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910944414.2A Active CN110717123B (en) | 2019-09-30 | 2019-09-30 | Page response method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110717123B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113076161A (en) * | 2021-04-08 | 2021-07-06 | 广州虎牙科技有限公司 | Page display method and device, storage medium and equipment |
| CN113821331A (en) * | 2020-06-18 | 2021-12-21 | 北京字节跳动网络技术有限公司 | Service acquisition method, device, terminal equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7346844B1 (en) * | 2000-01-21 | 2008-03-18 | International Business Machines, Corporation | Method and system for moving content in a content object stored in a data repository |
| CN102567092A (en) * | 2010-12-08 | 2012-07-11 | 微软公司 | Creation and termination of component scopes |
| CN108089904A (en) * | 2017-12-21 | 2018-05-29 | 上海新案数字科技有限公司 | A kind of displayed page extended method and equipment |
| CN109696867A (en) * | 2018-12-26 | 2019-04-30 | 上海司南卫星导航技术股份有限公司 | Method, user terminal and the GNSS device management system of user terminal processes GNSS device data |
| CN109814960A (en) * | 2018-12-21 | 2019-05-28 | 北京城市网邻信息技术有限公司 | A kind of page returning method, device, electronic equipment and storage medium |
-
2019
- 2019-09-30 CN CN201910944414.2A patent/CN110717123B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7346844B1 (en) * | 2000-01-21 | 2008-03-18 | International Business Machines, Corporation | Method and system for moving content in a content object stored in a data repository |
| CN102567092A (en) * | 2010-12-08 | 2012-07-11 | 微软公司 | Creation and termination of component scopes |
| CN108089904A (en) * | 2017-12-21 | 2018-05-29 | 上海新案数字科技有限公司 | A kind of displayed page extended method and equipment |
| CN109814960A (en) * | 2018-12-21 | 2019-05-28 | 北京城市网邻信息技术有限公司 | A kind of page returning method, device, electronic equipment and storage medium |
| CN109696867A (en) * | 2018-12-26 | 2019-04-30 | 上海司南卫星导航技术股份有限公司 | Method, user terminal and the GNSS device management system of user terminal processes GNSS device data |
Non-Patent Citations (2)
| Title |
|---|
| HONG XIN等: "The research on web service replacement based on workflow", 《 2014 IEEE 5TH INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING AND SERVICE SCIENCE》 * |
| 彭涛 等: "Jsp中作用域通信对象的研究与比较", 《太原师范学院学报(自然科学版)》 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113821331A (en) * | 2020-06-18 | 2021-12-21 | 北京字节跳动网络技术有限公司 | Service acquisition method, device, terminal equipment and medium |
| CN113076161A (en) * | 2021-04-08 | 2021-07-06 | 广州虎牙科技有限公司 | Page display method and device, storage medium and equipment |
| CN113076161B (en) * | 2021-04-08 | 2023-11-14 | 广州虎牙科技有限公司 | Page display method, device, storage medium and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110717123B (en) | 2022-04-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11909812B2 (en) | Application control method and apparatus, electronic device, and storage medium | |
| CN111581555B (en) | Document loading method, device, equipment and storage medium | |
| CN110390493B (en) | Task management method and device, storage medium and electronic equipment | |
| CN110717123B (en) | Page response method and device, electronic equipment and storage medium | |
| CN110781373A (en) | List updating method and device, readable medium and electronic equipment | |
| US20160080293A1 (en) | Accounts Control | |
| CN113254105A (en) | Resource processing method and device, storage medium and electronic equipment | |
| CN114625536A (en) | Video memory allocation method, device, medium and electronic equipment | |
| CN111580883B (en) | Application program starting method, device, computer system and medium | |
| CN109614089B (en) | Automatic generation method, device, equipment and storage medium of data access code | |
| WO2023056841A1 (en) | Data service method and apparatus, and related product | |
| CN113391860A (en) | Service request processing method and device, electronic equipment and computer storage medium | |
| CN109756525B (en) | Information subscription method and device | |
| CN115588064A (en) | Video generation method and device, electronic equipment and storage medium | |
| CN111813407B (en) | Game development method, game running device and electronic equipment | |
| CN114629951A (en) | Address service switching method and device, computer equipment and storage medium | |
| CN114327453A (en) | Page display method, device, equipment and storage medium | |
| CN110618772B (en) | View adding method, device, equipment and storage medium | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN110377654B (en) | Data request processing method and device, electronic equipment and computer-readable storage medium | |
| CN113127550A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN110941683A (en) | Method, device, medium and electronic equipment for acquiring object attribute information in space | |
| CN112306469A (en) | Barrier-free component construction method, device, equipment and storage medium | |
| CN114268653B (en) | Equipment calling method, device, equipment, medium and product | |
| CN113157695B (en) | Data processing method and device, readable medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |