CN110427237B - Method and device for cross-application access to target page and electronic equipment - Google Patents
Method and device for cross-application access to target page and electronic equipment Download PDFInfo
- Publication number
- CN110427237B CN110427237B CN201910691745.XA CN201910691745A CN110427237B CN 110427237 B CN110427237 B CN 110427237B CN 201910691745 A CN201910691745 A CN 201910691745A CN 110427237 B CN110427237 B CN 110427237B
- Authority
- CN
- China
- Prior art keywords
- application
- target page
- page
- access request
- matched
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the specification discloses a method, a device and electronic equipment for cross-application access to a target page, which are used for determining an access request for accessing the target page in a second application through a first application, wherein the access request comprises a page identifier of the target page; acquiring resources matched with the target page by utilizing the page identifier; and in the first application, rendering by using the matched resources, and displaying the target page.
Description
Technical Field
Embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a method, an apparatus, and an electronic device for accessing a target page across applications.
Background
Broadly, the application may be program software, a client, loaded on a platform for use by a user; in a narrow sense, an application may also be a sub-application with complete business functions under a client, where a user often encounters a situation that needs to jump between different applications during use of the client.
In the prior art, when a target page in a second application different from the first application is accessed in an opened first application, the second application can be triggered to start, and the target page is accessed in the second application; when the first application is to be returned or other applications are to be accessed continuously, the second application can be exited first, and then the first application is returned or other applications are started.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a method, an apparatus, and an electronic device for cross-application access to a target page, which are used to solve the problem in the prior art that different applications need to be repeatedly started when cross-application access to pages of other applications.
The embodiment of the specification adopts the following technical scheme:
the embodiment of the specification provides a method for accessing a target page across applications, which is applicable to a first application and comprises the following steps:
determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page;
acquiring resources matched with the target page by utilizing the page identifier;
and in the first application, rendering by using the matched resources, and displaying the target page.
The embodiment of the specification also provides a method for accessing a target page across applications, which is applicable to a first application and comprises the following steps:
determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
The embodiment of the specification also provides a device for accessing a target page across applications, which is suitable for a first application and comprises:
the method comprises the steps that a determining module determines an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page;
the acquisition module acquires resources matched with the target page by utilizing the page identification;
and the rendering module is used for rendering by utilizing the matched resources in the first application and displaying the target page.
The embodiment of the specification also provides a device for accessing a target page across applications, which is suitable for a first application and comprises:
the determining module is used for determining resource information corresponding to at least one target page of the second application displayed in the first application;
the creation module creates a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, the first application obtains resource information matched with the target page based on the corresponding relation, renders by utilizing resources corresponding to the resource information, and displays the target page.
The present embodiments also provide an electronic device comprising at least one processor and a memory, the memory storing a program and configured to cause the at least one processor to perform the steps of:
Determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page;
acquiring resources matched with the target page by utilizing the page identifier;
and in the first application, rendering by using the matched resources, and displaying the target page.
The present embodiments also provide an electronic device comprising at least one processor and a memory, the memory storing a program and configured to cause the at least one processor to perform the steps of:
determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
The above-mentioned at least one technical scheme that this description embodiment adopted can reach following beneficial effect:
determining an access request for accessing the target page through the first application, acquiring resources matched with the target page by utilizing a page identifier carried in the access request, further rendering the acquired resources in the first application, displaying the target page, and realizing cross-application access to the target page.
By adopting a mode of directly acquiring the matched resources of the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the repeated starting of the first application and the second application is avoided, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Drawings
The accompanying drawings, which are included to provide a further understanding of embodiments of the present disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the application. In the drawings:
FIG. 1 is a flowchart of a method for accessing a target page across applications according to an embodiment of the present disclosure;
FIG. 2 is a flowchart of a method for accessing a target page across applications according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a first application and a second application in a method for accessing a target page across applications according to an embodiment of the present disclosure;
FIG. 4 is a flowchart of a method for accessing a target page across applications according to an embodiment of the present disclosure;
Fig. 5 is a schematic structural diagram of an apparatus for accessing a target page across applications according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an apparatus for accessing a target page across applications according to an embodiment of the present disclosure.
Detailed Description
In the prior art, when a target page in a second application is accessed in a first application, the second application needs to be started, and the target page is accessed from the second application; and when the first application is to be returned or other applications are to be accessed continuously, the second application needs to be withdrawn first, then the first application is returned or other applications are started, and the user experience is poor.
Therefore, the embodiment of the specification provides a method, a device and an electronic device for cross-application access to a target page, which can render matched resources in a first application and display the target page in a second application by adopting a mode of directly acquiring the resources matched with the target page, so that the first application and the second application are prevented from being repeatedly started, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present specification and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present specification. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present application based on the embodiments herein.
The following describes in detail the technical solutions provided by the embodiments of the present specification with reference to the accompanying drawings.
Fig. 1 is a flowchart of a method for accessing a target page across applications provided in an embodiment of the present disclosure, where the method for accessing a target page across applications provided in the embodiment of the present disclosure is applicable to a first application.
S101: an access request for accessing a target page in a second application through a first application is determined, wherein the access request comprises a page identification of the target page.
In the embodiment of the present specification, the first application and the second application may be different applications having different service functions. The target page may be understood as a page of a second application that the user needs to access in the first application, and may specifically be any page in the second application.
The access request may be understood as an access requirement of the user to the target page according to a service access requirement, and specifically, the access request may be determined by an operation performed by the user in the page of the first application for accessing the target page.
The page identifier may be understood as feature data capable of characterizing the target page, and may specifically include a name of the target page, feature data in a preset format, or other feature data, such as a target page using 2-a.html as the page identifier.
As an application embodiment, the first application and the second application are different sub-applications under the same client;
or alternatively, the process may be performed,
the first application and the second application are different sub-applications under different clients.
In a specific application scene, a user can access a target page in a sub-application with different service functions under the same client in a page of a first application, and the target page is interaction between two sub-applications with different service functions under the same client. The user can also access a target page in the application with different service functions under different clients in the page of the first application, and the target page is interaction between the two applications with different service functions under different clients.
As an application embodiment, determining an access request to access a target page in a second application by a first application includes:
and receiving an access request of a user to the target page in the second application through the page of the first application.
The user can perform specified operation on the access target page according to the service access requirement in the page of the first application, and the page of the first application can determine the access request of the user to the target page according to the specified operation of the user.
As another application embodiment, receiving, by the page of the first application, an access request of a user to the target page in the second application, including:
receiving an access request of a user through a page of the first application;
judging whether the access request is an access request of a user to the target page in the second application;
if yes, intercepting the access request.
Specifically, each application includes at least one page, and in order to ensure the connection of service functions, access links for jumping access to other pages different from the page are provided in each page, and the service functions of the other pages are associated with the service functions of the page. The other pages may be different pages in the same application or different pages in different applications. The access link may specifically be a button, web site link, or other link form.
The page of the first application can receive the appointed operation of the user for jumping access links of other pages, such as clicking the links, so as to receive the access requests of the user for the other pages. In a specific application scenario, an access request of a user to other pages in the first application may be received, or an access request of a user to pages in other applications different from the first application, such as an access request to a target page, may be received.
After receiving an access request of a user, the page of the first application judges the received access request, and when the received access request is an access request of a target page in the second application, the access request is intercepted to determine the access request of the user to the target page.
As an application embodiment, before intercepting the access request, further comprising:
judging whether the target page is displayed in the first application;
if yes, intercepting the access request.
Specifically, the access request received by the page of the first application may be an access request to the target page by the first application, or may be an access request to the target application by the second application. If the access request of the first application to the target page is available, that is, the target page is displayed in the first application, the access request is intercepted. And if the access request to the target application is required by the second application, starting the second application, and accessing the target page in the second application according to the access request.
Determining whether to display the target page in the first application includes:
matching the stored configuration information in the first application by using the page identifier;
and judging whether the target page is displayed in the first application according to the matching result.
Configuration information associated with the target page is stored in the first application, and the configuration information is matched with the page identification. If the page identification can be matched with the stored configuration information, the target page can be displayed in the first application.
As an application embodiment, determining whether the access request is an access request of a user to the target page in the second application includes:
and judging whether the access request is an access operation of a user on a target object in the page of the first application, wherein the target object corresponds to the target page.
In a specific application scenario, a target object capable of accessing a target page is provided in a page of a first application, and the target object may specifically be an access button, an access link or other access forms, which are not specifically limited herein.
And judging whether the access request is an access operation of the user to the target object in the page of the first application or not, thereby judging whether the access request is an access request of the user to the target page or not.
The access operation may be a specified operation, such as a click operation, performed by the user on the target object of the target page in the page of the first application, so as to access the target page in the second application in the first application.
As an application embodiment, if it is determined that an access request for accessing a target page in a second application by a first application fails, the second application is directly started to access the target page by using the second application.
S103: and acquiring the resources matched with the target page by using the page identifier, wherein the configuration information is the configuration information stored in the first application.
In this embodiment of the present disclosure, the resource may be a configuration file required for rendering to obtain a target page, and the corresponding target page may be obtained by rendering the configuration file, so that the target page in the second application may be displayed in the first application.
As an application embodiment, the obtaining, by using the page identifier, a resource matching the target page includes:
acquiring configuration information corresponding to the target page according to the page identifier;
and acquiring the resources matched with the target page by utilizing the configuration information.
The configuration information may be understood as related information of the resources matched with the associated target page set in the first application, and may specifically be a page identifier, version information of the second application, a storage address of the matched resources, or other information, which is not specifically limited herein. The page identifier can correspond to an access request of a user to the target page, and the configuration information corresponding to the target page can be determined in the stored configuration information through the page identifier, so that the matched resources of the target page can be obtained through the configuration information.
The page identifier may be used as an identifier of the target page, or may reflect the second application corresponding to the target page. Specifically, the page identifier may further carry version information of the target page and the second application.
In a specific application scenario, the obtaining, by using the page identifier, a resource that is matched with the target page may include:
the matched resource is obtained from at least one of a content distribution network and an offline resource store.
The content delivery network (CDN, content Delivery Network) is constructed on the network, and by means of the edge servers deployed in various places, the users can obtain the required content nearby through the load balancing, content distribution, scheduling and other functional modules of the center platform, so that network congestion is reduced, and the access response speed and hit rate of the users are improved.
Offline resource storage (JET) is an offline resource acceleration application, and is implemented by taking a URL (Uniform Resource Locator ) as a path of a static resource of a page, packaging the static resource into an offline package, and performing offline acceleration loading on a resource matched with a target page.
By storing the page resources in the application in the content distribution network and the offline resource storage, the online or offline storage of the resources is realized, the online storage can update the types, versions and the like of the stored page resources, and the offline stored page resources can realize the acceleration loading.
As an application embodiment, the obtaining, by using the configuration information, the resource matched with the target page includes:
determining a storage address of the resource by using the configuration information;
downloading the resource under the storage address.
After the configuration information corresponding to the target page is determined, the storage address of the resource matched with the target page can be determined according to the configuration information, for example, the storage address can be a storage address in a content distribution network or offline resource storage, and the required resource can be acquired through the storage address.
As an application embodiment, the method further comprises:
Determining version information of the target page by utilizing the stored configuration information;
judging whether the version information of the target page is matched with the version information of the resource under the storage address;
if not, updating the version information of the target page in the stored configuration information.
The resources stored in the content distribution network can be updated in real time according to the update of the version of the application, and if the version information of the target page corresponding to the configuration information cannot be matched with the version information of the resources matched in the content distribution network or the offline resource storage, the resources of the latest version in the content distribution network can be loaded into the first application, or the resources of the target page corresponding to the version can be requested to be acquired from the second application.
In a specific application scene, there may be a situation that the configuration information corresponding to the target page is not stored in the first application, in this case, the first application may directly query the resources matched with the target page in the content distribution network and the offline resource storage through the page identifier, and if the resources can be queried, the queried resources are directly downloaded to the first application; if the target page can not be queried, the first application can also send a resource acquisition request carrying the page identifier to the second application, and acquire the resource matched with the target page from the second application in real time.
The first application may send a resource obtaining request to the second application, which may be that the first application sends a resource obtaining request to a server or CDN corresponding to the second application, where the server or CDN corresponding to the second application obtains a corresponding resource from the second application, and the server or CDN corresponding to the second application sends the resource corresponding to the page identifier to the first application.
As an application embodiment, if the acquisition of the resource matched with the target page by using the page identifier fails, the second application is started to access the target page by using the second application.
S105: and in the first application, rendering by using the matched resources, and displaying the target page.
In the embodiment of the specification, the frame logic of the SuperApp is added into the first application, so that the first application has the capability of opening and accessing pages in other applications different from the first application inside the application. In the first application, the matched resources are rendered, and the rendering logic and the rendering framework can be realized by the framework logic of the SuperApp, so that the target page in the second application can be rendered in the first application.
The SuperApp is a cross-platform and cross-system open application program, has infinite functions and infinite volume expandability, and has strong openness. Therefore, by adding the frame logic of the SuperApp in the first application, the target page can be obtained by rendering the matched resources in the first application without starting the second application.
As an application embodiment, the method further comprises:
and if the rendering by using the matched resources fails in the first application, starting the second application so as to access the target page by using the second application.
In the process of obtaining the target page in the first application, if any step fails, a second application is started, and the target page is accessed from the second application.
According to the method for accessing the target page across the applications, which is provided by the embodiment of the specification, by adopting a mode of directly acquiring the resources matched with the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the repeated starting of the first application and the second application is avoided, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Fig. 2 is a flowchart of a method for accessing a target page across applications provided in an embodiment of the present disclosure, where the method for accessing a target page across applications provided in the embodiment of the present disclosure is applicable to a first application.
S201: and determining resource information corresponding to at least one target page of the second application displayed in the first application.
In the embodiment of the present disclosure, when the frame logic of the SuperApp is added to the first application, at least one target page of the second application displayed in the first application may be determined, where in a specific application scenario, the target page of the second application displayed in the first application may have a business association with a page of the first application.
The resource information may be understood as configuration information associated with a page of the second application, through which a resource matched to the page of the second application displayed in the first application may be acquired. The resource information may be page identification of a page, version information of a corresponding application, a storage address of a matched resource, and the like, which are not particularly limited herein.
S203: and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
By creating the corresponding relation between the first application and the resource information, the first application can inquire the resources matched with the target page according to the corresponding relation, so that the access logic between pages of the cross-application can be accurately operated.
According to the method for accessing the target page across the applications, which is provided by the embodiment of the specification, by adopting a mode of directly acquiring the resources matched with the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the repeated starting of the first application and the second application is avoided, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Fig. 3 is a schematic structural diagram of an offline package application in a method for accessing a target page across applications according to an embodiment of the present disclosure, where App1 may be a first application described in the foregoing embodiment of the present disclosure, and App2 may be a second application described in the foregoing embodiment of the present disclosure.
S301: and storing the page matched resources in the offline package applications App1 and App2 in the CDN/JET.
In the embodiment of the present specification, an offline package application may be understood as an application with a complete service function and capable of running independently, where the application includes all pages, resources (pictures, styles, scripts, etc.) files in the pages of the service function, and packages and combines the files together to form an application.
The offline package application can be an independent sub-application with different service functions under the same client, and the influence of network jitter on service quality can be reduced by packing pages with different service functions under the client into the offline package application.
And the two offline package applications App1 and App2 each comprise at least one page, for example, app1 comprises pages 1-a.html and 1-b.html, app2 comprises pages 2-a.html and 2-b.html, and resources matched with the pages in each application are stored in CDN/JET. The frame logic of the SuperApp is added into the offline package application App1, so that the App1 has the capability of opening pages of other applications different from App1 in the application.
The resources matched by pages 1-a.html may include 1-a.css/1-a.js, the resources matched by pages 1-b.html may include 1-b.css/1-b.js, and the resources matched by pages 2-a.html may include 2-a.css/2-
The resources that page 2-b.html matches may include 2-b.css/2-b.js.
S303: the offline package application App1 is started.
S305: when an access request of a user accessing a target page in App2 through App1 is received in the page of App1, entering a Superhtml page, and acquiring configuration information corresponding to the target page.
When a user needs to enter a target page (2-a.html) in an App2 through interaction means such as clicking in a page of the App1, entering a SuperApp flow, intercepting an access request of the user to the target page to a dynamic Superhtml page, searching resources matched with the target page through the page and the access request, loading, analyzing and rendering the matched resources in an offline package application App1, and displaying the target page.
Specifically, in the SuperHtml page, the storage address of the resource matched with the target page is determined through configuration information, then the resource matched with the target page is downloaded (load) and copied (Scriping) into the first application, the resource matched with the run (run) is rendered, and the target page is displayed.
Fig. 4 is a flowchart of a method for accessing a target page across applications provided in an embodiment of the present disclosure, where the method for accessing a target page across applications provided in the embodiment of the present disclosure is applicable to a first application.
S401: and intercepting an access request of a user to the page.
S403: and analyzing the access request to obtain a page identifier corresponding to the target page.
S405: judging whether to allow the SuperApp mode to open the target page or not through the page identification.
In a specific application scenario, determining whether to allow the SuperApp mode to open the target page may include:
judging whether the target page is displayed in the first application;
if yes, allowing the SuperApp mode to open the target page.
S407: if yes, the access request is intercepted to a Superhtml page.
S409: and acquiring the storage address of the resource matched with the target page by using the page identifier.
In a specific application scenario, the obtaining the storage address of the resource matched with the target page may include:
obtaining configuration information corresponding to the target page by utilizing the page identification matching;
and determining the storage address of the resource matched with the target page according to the configuration information.
S411: downloading the matched resource under the storage address.
S413: and rendering the matched resources in the first application, and displaying the target page.
S415: if any of the steps S405 to S413 fails to be executed, the second application is directly started, and the target page is triggered to be entered in the second application.
According to the method for accessing the target page across the applications, which is provided by the embodiment of the specification, by adopting a mode of directly acquiring the resources matched with the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the repeated starting of the first application and the second application is avoided, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Fig. 5 is a schematic structural diagram of an apparatus for accessing a target page across applications according to an embodiment of the present disclosure, where the apparatus for accessing a target page across applications provided in the embodiment of the present disclosure is applicable to a first application.
A determining module 502, configured to determine an access request for accessing, by a first application, a target page in a second application, where the access request includes a page identifier of the target page;
an obtaining module 504, configured to obtain a resource matching the target page by using the page identifier;
and a rendering module 506, in the first application, for rendering by using the matched resource, and displaying the target page.
According to the device for accessing the target page across the applications, which is provided by the embodiment of the specification, by adopting a mode of directly acquiring the resources matched with the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the first application and the second application are prevented from being repeatedly started, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Fig. 6 is a schematic structural diagram of an apparatus for accessing a target page across applications according to an embodiment of the present disclosure, where the apparatus for accessing a target page across applications provided in the embodiment of the present disclosure is applicable to a first application.
A determining module 602, configured to determine resource information corresponding to at least one target page of a second application displayed in the first application;
the creating module 604 creates a correspondence between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, the first application obtains resource information matched with the target page based on the correspondence, renders by using resources corresponding to the resource information, and displays the target page.
According to the device for accessing the target page across the applications, which is provided by the embodiment of the specification, by adopting a mode of directly acquiring the resources matched with the target page, the matched resources can be rendered in the first application, and the target page in the second application is displayed, so that the first application and the second application are prevented from being repeatedly started, the limitation that the target page must be displayed in the second application is broken under the condition that the existing business logic in the first application is not influenced, the user experience is improved, and the user traffic resources are saved.
Based on the same inventive concept, the present embodiments also provide an electronic device comprising at least one processor and a memory, the memory storing a program and configured to be executed by the at least one processor to:
determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page;
acquiring resources matched with the target page by utilizing the page identifier;
and in the first application, rendering by using the matched resources, and displaying the target page.
The other functions of the processor may also be referred to the content described in the above embodiments, which is not described herein.
Based on the same inventive concept, the present embodiments also provide a computer-readable storage medium including a program for use with an electronic device, the program being executable by a processor to perform the steps of:
determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page;
acquiring resources matched with the target page by utilizing the page identifier;
And in the first application, rendering by using the matched resources, and displaying the target page.
The other functions of the processor may also be referred to the content described in the above embodiments, which is not described herein.
Based on the same inventive concept, the present embodiments also provide an electronic device comprising at least one processor and a memory, the memory storing a program and configured to be executed by the at least one processor to:
determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
The other functions of the processor may also be referred to the content described in the above embodiments, which is not described herein.
Based on the same inventive concept, the present embodiments also provide a computer-readable storage medium including a program for use with an electronic device, the program being executable by a processor to perform the steps of:
Determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
The other functions of the processor may also be referred to the content described in the above embodiments, which is not described herein.
In the 90 s of the 20 th century, improvements to one technology could clearly distinguish between improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) and software (e.g., improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable Gate Array, FPGA)) is an integrated circuit whose logic function is determined by the programming of the device by a user. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (16)
1. A method for accessing a target page across applications, suitable for a first application, comprising:
determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page; the target page is any page in the second application;
acquiring resources matched with the target page by utilizing the page identifier; the resource is a configuration file required for rendering the target page;
In the first application, rendering by using the matched resources, and displaying the target page; the first application has a logical framework of a super application.
2. The method of claim 1, the first application and the second application being different sub-applications under the same client;
or alternatively, the process may be performed,
the first application and the second application are different sub-applications under different clients.
3. The method of claim 1, determining an access request to access, by the first application, a target page in the second application, comprising:
and receiving an access request of a user to the target page in the second application through the page of the first application.
4. The method of claim 3, receiving, by the page of the first application, a user access request to the target page in the second application, comprising:
receiving an access request of a user through a page of the first application;
judging whether the access request is an access request of a user to the target page in the second application;
if yes, intercepting the access request.
5. The method of claim 4, determining whether the access request is a user access request to the target page in the second application, comprising:
And judging whether the access request is an access operation of a user on a target object in the page of the first application, wherein the target object corresponds to the target page.
6. The method of claim 4, further comprising, prior to intercepting the access request:
judging whether the target page is displayed in the first application;
if yes, intercepting the access request.
7. The method of claim 6, determining whether to display the target page in the first application, comprising:
matching the stored configuration information in the first application by using the page identifier;
and judging whether the target page is displayed in the first application according to the matching result.
8. The method of claim 1, utilizing the page identity to obtain resources matching the target page, comprising:
acquiring configuration information corresponding to the target page according to the page identifier, wherein the configuration information is stored in a first application;
and acquiring the resources matched with the target page by utilizing the configuration information.
9. The method of claim 8, utilizing the configuration information to obtain resources that match the target page, comprising:
Determining a storage address of the resource by using the configuration information;
downloading the resource under the storage address.
10. The method of claim 9, further comprising:
determining version information of the target page by utilizing the stored configuration information;
judging whether the version information of the target page is matched with the version information of the resource under the storage address;
if not, updating the version information of the target page in the stored configuration information.
11. The method of claim 1, utilizing the page identity to obtain resources matching the target page, comprising:
the matched resource is obtained from at least one of a content distribution network and an offline resource store.
12. A method for accessing a target page across applications, suitable for a first application, comprising:
determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
13. An apparatus for accessing a target page across applications, suitable for a first application, comprises:
the method comprises the steps that a determining module determines an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page; the target page is any page in the second application;
the acquisition module acquires resources matched with the target page by utilizing the page identification; the resource is a configuration file required for rendering the target page;
the rendering module is used for rendering by utilizing the matched resources in the first application and displaying the target page; the first application has a logical framework of a super application.
14. An apparatus for accessing a target page across applications, suitable for a first application, comprises:
the determining module is used for determining resource information corresponding to at least one target page of the second application displayed in the first application;
the creation module creates a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, the first application obtains resource information matched with the target page based on the corresponding relation, renders by utilizing resources corresponding to the resource information, and displays the target page.
15. An electronic device comprising at least one processor and a memory, the memory storing a program and configured to cause the at least one processor to perform the steps of:
determining an access request for accessing a target page in a second application through a first application, wherein the access request comprises a page identifier of the target page; the target page is any page in the second application;
acquiring resources matched with the target page by utilizing the page identifier; the resource is a configuration file required for rendering the target page;
in the first application, rendering by using the matched resources, and displaying the target page; the first application has a logical framework of a super application.
16. An electronic device comprising at least one processor and a memory, the memory storing a program and configured to cause the at least one processor to perform the steps of:
determining resource information corresponding to at least one target page of a second application displayed in the first application;
and creating a corresponding relation between the first application and the resource information, so that when the first application receives an access request for accessing a target page in the second application, acquiring the resource information matched with the target page based on the corresponding relation, and rendering by utilizing resources corresponding to the resource information to display the target page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910691745.XA CN110427237B (en) | 2019-07-29 | 2019-07-29 | Method and device for cross-application access to target page and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910691745.XA CN110427237B (en) | 2019-07-29 | 2019-07-29 | Method and device for cross-application access to target page and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110427237A CN110427237A (en) | 2019-11-08 |
| CN110427237B true CN110427237B (en) | 2023-10-20 |
Family
ID=68411252
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910691745.XA Active CN110427237B (en) | 2019-07-29 | 2019-07-29 | Method and device for cross-application access to target page and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110427237B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988284B (en) * | 2021-05-13 | 2021-08-24 | 太平金融科技服务（上海）有限公司 | Application program starting method and device, computer equipment and storage medium |
| CN116384992A (en) * | 2021-05-19 | 2023-07-04 | 支付宝(杭州)信息技术有限公司 | Information sending method, device, equipment and medium |
| CN114896006B (en) * | 2022-04-27 | 2023-06-09 | 青岛海尔科技有限公司 | Page menu creation method and device, storage medium and electronic device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103399788A (en) * | 2013-08-07 | 2013-11-20 | 广东欧珀移动通信有限公司 | Cross-application control method and system for intelligent terminal |
| CN104281677A (en) * | 2014-09-29 | 2015-01-14 | 百度在线网络技术（北京）有限公司 | Page displaying method and device |
| CN106357591A (en) * | 2015-07-16 | 2017-01-25 | 中兴通讯股份有限公司 | Inter-application data access method and device |
| CN106919634A (en) * | 2016-06-12 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Across the method and web browser of Application share data |
| CN107203630A (en) * | 2017-05-31 | 2017-09-26 | 北京安云世纪科技有限公司 | Application program page collecting method, device and corresponding mobile terminal |
| CN108572985A (en) * | 2017-03-13 | 2018-09-25 | 腾讯科技（深圳）有限公司 | A kind of page display method and device |
| CN108804113A (en) * | 2018-06-07 | 2018-11-13 | 东软集团股份有限公司 | Dispose the method, apparatus and storage medium and electronic equipment that micro services are applied |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9038138B2 (en) * | 2012-09-10 | 2015-05-19 | Adobe Systems Incorporated | Device token protocol for authorization and persistent authentication shared across applications |
| CN107085580B (en) * | 2016-02-16 | 2021-11-09 | 阿里巴巴集团控股有限公司 | Method for displaying page by client and client |
| CN105808725B (en) * | 2016-03-08 | 2019-08-13 | 腾讯科技（深圳）有限公司 | A kind for the treatment of method and apparatus of application message |
| CN107092610A (en) * | 2016-05-24 | 2017-08-25 | 口碑控股有限公司 | The searching method and device, the sorting technique of APP application icons and device of APP applications |
| CN107451162B (en) * | 2016-06-01 | 2020-12-18 | 阿里巴巴（中国）有限公司 | Network resource access device, hybrid device and method |
| CN108846131A (en) * | 2018-07-03 | 2018-11-20 | 深圳鼎盛电脑科技有限公司 | Weex page rendering method, apparatus, terminal and storage medium |
| CN109284089B (en) * | 2018-08-30 | 2022-04-05 | 上海艾融软件股份有限公司 | System and method for realizing e-commerce platform based on micro-service technology |
-
2019
- 2019-07-29 CN CN201910691745.XA patent/CN110427237B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103399788A (en) * | 2013-08-07 | 2013-11-20 | 广东欧珀移动通信有限公司 | Cross-application control method and system for intelligent terminal |
| CN104281677A (en) * | 2014-09-29 | 2015-01-14 | 百度在线网络技术（北京）有限公司 | Page displaying method and device |
| CN106357591A (en) * | 2015-07-16 | 2017-01-25 | 中兴通讯股份有限公司 | Inter-application data access method and device |
| CN106919634A (en) * | 2016-06-12 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Across the method and web browser of Application share data |
| CN108572985A (en) * | 2017-03-13 | 2018-09-25 | 腾讯科技（深圳）有限公司 | A kind of page display method and device |
| CN107203630A (en) * | 2017-05-31 | 2017-09-26 | 北京安云世纪科技有限公司 | Application program page collecting method, device and corresponding mobile terminal |
| CN108804113A (en) * | 2018-06-07 | 2018-11-13 | 东软集团股份有限公司 | Dispose the method, apparatus and storage medium and electronic equipment that micro services are applied |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110427237A (en) | 2019-11-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10445083B2 (en) | Application containers with dynamic sub-package loading | |
| EP3403178B1 (en) | Identifiers across application instances | |
| CN110427237B (en) | Method and device for cross-application access to target page and electronic equipment | |
| CN107092475B (en) | Calling method and device of interactive control | |
| EP3606010B1 (en) | Method and apparatus for processing web application package | |
| CN111475142B (en) | Method, device and equipment for generating applet file package | |
| CN111796823A (en) | Method and device for updating page and displaying page and page maintenance system | |
| CN108549562A (en) | A kind of method and device of image load | |
| US20210173681A1 (en) | Method and device for displaying interface, electronic equipment, server, and storage medium | |
| CN107479868B (en) | Interface loading method, device and equipment | |
| CN110990105A (en) | Interface display method and device, electronic equipment and storage medium | |
| CN111897623B (en) | Cluster management method, device, equipment and storage medium | |
| CN111273965B (en) | Container application starting method, system and device and electronic equipment | |
| CN113852498B (en) | Method and device for deploying, managing and calling components | |
| CN111338655B (en) | Installation package distribution method and system | |
| CN110874322B (en) | Test method and test server for application program | |
| CN110022351B (en) | Service request processing method and device | |
| WO2023124657A1 (en) | Micro-application running method and apparatus, device, storage medium, and program product | |
| CN111209022A (en) | Resource publishing and acquiring method, device and equipment | |
| CN116302230A (en) | Page display method, device and equipment | |
| CN108681492A (en) | Data processing method and device | |
| CN110502251B (en) | Application installation method and device | |
| CN112596780A (en) | Service execution method and device | |
| CN112698882A (en) | Page component loading method and device | |
| CN117519912B (en) | Mirror image warehouse deployment method, device, storage medium and 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 | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40016838 Country of ref document: HK |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201012 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201012 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |