CN111090823B

CN111090823B - Page application integration system, application access method, device and equipment

Info

Publication number: CN111090823B
Application number: CN201911338890.6A
Authority: CN
Inventors: 钟星斗
Original assignee: Guangzhou Baiguoyuan Information Technology Co Ltd
Current assignee: Guangzhou Baiguoyuan Information Technology Co Ltd
Priority date: 2019-12-23
Filing date: 2019-12-23
Publication date: 2024-02-09
Anticipated expiration: 2039-12-23
Also published as: CN111090823A

Abstract

The embodiment of the invention discloses an integrated system of page application, and an application access method, device and equipment. Wherein the integrated system comprises: accessing an entry layer, a container management layer and a page display layer; the access entry layer determines a target container management component in the container management layer according to an access address of an application to be accessed; the container management layer searches a target container packed with the application to be accessed through a target container management component, and determines the access content of the application to be accessed through the target container; the page display layer displays the access content in the front end interface area corresponding to the target container. According to the technical scheme provided by the embodiment of the invention, various page applications are integrated in a containerization mode, application access under different integration modes is realized, the safety and diversity of application integration are ensured, and meanwhile, the page display layer sets corresponding front-end interface areas for different containers, so that the access content of the application to be accessed is directly loaded, and the time consumption of application integration and access is reduced.

Description

Page application integration system, application access method, device and equipment

Technical Field

The embodiment of the invention relates to the field of management of page applications, in particular to an integrated system of page applications, and an application access method, device and equipment.

Background

With the development of internet technology, a page application (web application) running on a web browser gradually becomes a mainstream application program with the characteristics of no installation, no upgrading, convenient loading and release according to requirements and the like; with the development of more and more web applications, in order to make users more friendly and convenient to manage various web applications, integrating business-related web applications into one large web application system is a current urgent problem to be solved.

Meanwhile, since the purpose of the design of the web browser is mainly information propagation, related standards and implementations are also mainly around information propagation and linking. In recent years, web browser standards and implementation mechanisms increase the support for web applications, but the technical scheme for realizing the web applications is not completely standardized, and web applications realized by adopting a plurality of different technical schemes exist; at this time, how to integrate web applications implemented by different technical schemes is a problem to be faced and solved by large-scale web application integration.

Currently, web applications are typically integrated using two schemes:

1) All web applications are gradually changed into the same technical scheme to be realized, or the project can be specified to only use the same technical scheme at the beginning. In this mode, each web application becomes an internal logic module of the integrated system, where common parts of the functions of each module use the same code or the same version of external dependency package, and finally, multiple modules are integrated into a large application integrated system. The scheme has the main advantages that different web applications are simple and direct in interaction, convenient in code multiplexing and easy to implement in developing technical standards and system interface specifications; the method has the defects that along with the growth of an integrated system, the construction and the test of each web application are slower and slower, the upgrading of a common code and an external dependence package can be carried over to the whole integrated system, and great burden and risk are caused to the subsequent maintenance and development of the integrated system.

2) The web applications realized by different technical schemes are loaded to the integrated system by taking an internal embedded frame (i.e. an element of < iframe >) as a carrier, and at the moment, the embedded main page of the integrated system switches different web applications by dynamically changing the embedded page address of the < iframe >; the manner of using the < iframe > at this time can be divided into a single-activity mechanism that repeatedly uses a single < iframe > and a multiple-activity mechanism that different web applications use their own < iframes >. The main advantage of the scheme is that the technical scheme adopted for realizing the web application is not limited; the disadvantage is that the web application needs to be reloaded each time it is switched in under the single-activity mechanism, and the web application needs to be cleaned each time it is switched out, so that the loading of the web application is time-consuming, while in the multi-activity mechanism, there may be a plurality of embedded web applications in the main page, resulting in a higher occupation of system resources by the page.

Disclosure of Invention

The embodiment of the invention provides an integrated system of page application, and an application access method, device and equipment, which can reduce the time consumption of application integration and access and improve the safety and diversity of application integration.

In a first aspect, an embodiment of the present invention provides an integrated system for a page application, where the integrated system includes: accessing an entry layer, a container management layer and a page display layer; wherein,

the access entry layer determines a target container management component in the container management layer according to an access address of an application to be accessed; the container management layer searches a target container packed with the application to be accessed through the target container management component, and determines the access content of the application to be accessed through the target container; and the page display layer displays the access content in a front end interface area corresponding to the target container.

In a second aspect, an embodiment of the present invention provides an application access method, which is applied to the integrated system of the page application described in the first aspect, where the method includes:

determining a corresponding target container management component of an application to be accessed in a container management layer through an access entry layer according to an access address of the application to be accessed;

Searching a target container which packages the application to be accessed through the target container management component, and determining access content of the application to be accessed according to the access address through the target container;

and displaying the access content in the front end interface area corresponding to the target container through a page display layer.

In a third aspect, an embodiment of the present invention provides an application access device configured in the integrated system of a page application described in the first aspect, where the device includes:

the container component determining module is used for determining a target container management component corresponding to the application to be accessed in the container management layer according to the access address of the application to be accessed through the access entry layer;

the access content determining module is used for searching out a target container which is packed with the application to be accessed through the target container management component, and determining the access content of the application to be accessed according to the access address through the target container;

and the access content display module is used for displaying the access content in the front end interface area corresponding to the target container through the page display layer.

In a fourth aspect, an embodiment of the present invention provides an apparatus, including:

One or more processors;

a storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the application access method described in any embodiment of the present invention.

In a fifth aspect, an embodiment of the present invention provides a computer readable storage medium, on which a computer program is stored, where the program is executed by a processor to implement the application access method according to any embodiment of the present invention.

According to the integrated system of the page application, the device and the equipment, the containers and the container management components are arranged in the container management layer, the corresponding page application is packaged in each container, the container management components manage the containers, at the moment, the access entry layer firstly determines the target container management component of the application to be accessed in the container management layer according to the access address of the application to be accessed, the target container management component is used for searching the target container packaged with the application to be accessed in the managed components, the access content of the application to be accessed is determined through the target container, the page display layer displays the access content in the front end interface area corresponding to the target container, therefore, various page applications are integrated in a containerized mode, the same technical scheme is not required to be adopted to realize different page applications or the page application is only accessed in the integrated system in an internal embedded mode, the application access under different integrated modes is realized by adaptively increasing the containers to package the page applications under different external types in the integrated system, the safety and the diversity of application integration are ensured, and meanwhile, the page display layer is used for setting the corresponding front end interface area of the application to be accessed directly, and the time consumption of the application to be accessed is reduced.

Drawings

Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:

FIG. 1A is a schematic diagram of an integrated system for page applications according to a first embodiment of the present invention;

FIG. 1B is a schematic diagram of an integrated system for another page application according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of an integrated system for page applications according to a second embodiment of the present invention;

fig. 3 is a flowchart of an application access method according to a third embodiment of the present invention;

fig. 4 is a flowchart of an application access method according to a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of an application access device according to a fifth embodiment of the present invention;

fig. 6 is a schematic structural diagram of an apparatus according to a sixth embodiment of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings. Furthermore, embodiments of the invention and features of the embodiments may be combined with each other without conflict.

Example 1

Fig. 1A is a schematic architecture diagram of an integrated system for page application according to a first embodiment of the present invention. The embodiment can be applied to any case of integrating various web applications. Specifically, referring to FIG. 1A, the page application integration system 10 may include: access entry layer 110, container management layer 120, and page presentation layer 130.

Wherein the access entry layer 110 determines a target container management component in the container management layer 120 according to an access address of an application to be accessed; the container management layer 120 searches a target container packed with the application to be accessed through a target container management component, and determines the access content of the application to be accessed through the target container; the page presentation layer 130 presents the access content in a front end interface region corresponding to the target container.

Specifically, the page application in the embodiment may refer to a developed web application running on a web browser, where the web application may be directly started in the web browser without being installed and updated on a terminal by a user, and corresponding application content may be loaded as required; because of the large number of web applications developed, each web application related to the service needs to be integrated into one large-scale web application system, so that users can use and manage more conveniently, the embodiment integrates each developed page application by designing an integrated system 10 of the page application, and realizes the access function under each page application, and at this time, the embodiment adopts a layering technology to design the functions of the integrated system 10, specifically, the access entry layer 110, the container management layer 120 and the page display layer 130, for different types of the access function.

Optionally, the access entry layer 110 is mainly responsible for initializing data and functions of the integrated system 10, and simultaneously monitors address changes of corresponding browsers when a user triggers access to different page applications in a front-end interface of the integrated system 10, so as to determine the application to be accessed in the current access.

Specifically, as shown in fig. 1B, in this embodiment, for different functions responsible for the access entry layer 110, a corresponding initialization module 111 and a main routing module 112 may be respectively set in the access entry layer 110, where the initialization module 111 is used to control function initialization of the integrated system 10 under different hierarchies, and the main routing module 112 is used to monitor an access address of an application to be accessed, and determine a target container management component corresponding to the application to be accessed by using a mapping address mechanism.

Illustratively, the initialization module 111 is mainly responsible for initial data loading in each page application accessed in the integrated system 10, and creating container instances and main routing module instances for packaging corresponding page applications in the container management layer 120 and initializing operations thereof; meanwhile, when accessing each page application, the integrated system 10 sets a mapping address mechanism between an access address of each page application and a container management component in advance according to the access condition, so as to find container management components of different applications to be accessed, at this time, the main routing module 112 monitors a browser address at the current time, that is, an access address of the application to be accessed, and determines a target container management component corresponding to the application to be accessed according to a matching condition between the access address and the container management component in the preset mapping address mechanism, so as to directly use the target container management component to access the application to be accessed.

Further, in order to perform classification management under different context isolation states for each page application implemented by adopting different technical schemes, the container management layer 120 in this embodiment may set corresponding containers for the context isolation states of each page application to package each page application, so as to access the page application into the integrated system 10 in this embodiment; at this time, the container may refer to a standardized and isolatable software running environment, in which different page applications may be packaged according to container standards, and then run in a shared software and hardware environment (like a computer, an operating system, a network, etc.) in an isolated sandbox, where a page application running in a sandbox will not conflict with a page application running in another sandbox (such as resource preemption, locking, modification, etc.), and the container further provides a uniform interaction mechanism between containers, so that multiple containers are integrated together to form a larger system; in this embodiment, each page application is packaged, constructed, integrated, deployed, etc. according to a certain container standard, and is connected to the integrated system 10, so as to implement containerization integration of the page application, and further integrate the page applications implemented by different technical schemes through different containers, when the integrated system 10 needs to be connected to a new page application, it may be directly determined whether a container suitable for packaging the page application exists in the container management layer 120, if not, a new container is redefined in the container management layer 120 according to the context isolation state of the page application, so as to package the new page application, and ensure the expandability of the page application on the integrated system 10.

Meanwhile, in order to implement interaction between different containers and the page applications packaged by the containers, in this embodiment, each container in the container management layer 120 is provided with a corresponding container interface, where application attributes and functional methods supported by the container are defined in the container interface; only the page applications packaged by the container provided with the container interface can access the integrated system 10, and the application attributes and functional methods defined in the container interface are shown in the following tables 1 and 2:

table 1 application attributes of container interface

Table 2 functional method of container interface

In addition, in order to facilitate management of containers under the same type, in this embodiment, a corresponding container management component is further provided in the container management layer 120, and one container management component may manage multiple containers under the corresponding type, so when the access portal layer 110 receives an access address of an application to be accessed, a target container management component corresponding to the access address may be determined from the container management layer 120 first, and a target container in which the application to be accessed is packaged is further searched by the target container management component, so as to ensure accuracy of the target container.

Further, the page display layer 130 in this embodiment is mainly responsible for corresponding display in the front-end interface on the integrated system 10, and at this time, the page display layer 130 sets different containers in the container management layer 120, and after packaging corresponding page applications, different interface tags may be used to set corresponding front-end interface areas for the page applications packaged by each container in the front-end interface, so that after determining the access content of the application to be accessed through the target container, the page display layer may display the access content of the application to be accessed in the front-end interface area corresponding to the target container, so as to implement access of different page applications.

At this time, the page display layer 130, in addition to setting the front end interface area of the corresponding access content displayed by each page application, provides a switching entry for the access content under different page applications on the front end interface, at this time, the page display layer 130 presets the switching display of the access content under different containers in the container management layer 120 in the front end interface, that is, sets a navigation schematic diagram of different page applications on the front end interface, and the user selects the application to be accessed in this time in the navigation schematic diagram, so that the access entry layer 110 can receive the access address of the application to be accessed after switching according to the switching operation of the user on different page applications in the front end interface, and further, according to the same access process described above, display the access content of the application to be accessed after switching again. At this time, the access content of the page application packaged by only one container generally disposed on the front-end interface on the page display layer 130 is visible to the user, and when the page application packaged by other containers is to be displayed on the front-end interface, a navigation control element may be disposed on the page display layer 130, and the switching of the application to be accessed under different containers is controlled by the navigation control element; by way of example, the navigation control element may be a tab navigation button or menu item in the front-end interface, or the like.

Specifically, when the integrated system 10 is built, firstly, a plurality of container standards can be defined in the container management layer 120 according to the context isolation state of the existing page application, so as to realize different container architectures in the container management layer 120, secondly, corresponding container management components are set in the container management layer 120 according to the type of the constructed container, so as to realize the collection management of the container of the same type, further, an initialization module 111 in the access entry layer 110 and a main routing module 112 triggered by the integrated system 10 after entering the first page of the system are set, so as to realize the initialization of the container access dispatch and the system data function under different page applications, and meanwhile, according to different containers in the container management layer 120, each page application is accessed in the integrated system 10, and the mapping relation between the access address and the container management component of each page application is correspondingly recorded, so as to set the navigation of each page application and the content display of the application to be accessed in the page display layer 130, further, the integration and access of different page applications on the integrated system 10 are realized, the time consumption of the application is reduced, and the security and diversity of the application are improved.

According to the technical scheme provided by the embodiment, a plurality of containers and container management components are arranged in the container management layer, each container is internally packaged with a corresponding page application, each container management component manages a plurality of containers, at this time, the access entry layer firstly determines a target container management component for managing the application to be accessed in the container management layer according to the access address of the application to be accessed, the target container management component searches the plurality of components managed by the target container management component for packing the target container for packing the application to be accessed, and further determines the access content of the application to be accessed through the target container, and the page display layer displays the access content in the front end interface area corresponding to the target container, so that various page applications are integrated in a containerized mode, different page applications are not required to be realized or page applications are only accessed in an internal embedded mode in an integrated system, application access under different external types is realized by adaptively increasing the containers in the integrated system, the safety and diversity of application integration are ensured, and simultaneously the page display layer sets the corresponding front end interface area for different containers, so that the time consumption of accessing the application to be accessed is reduced, and the access content of the integrated application is directly loaded.

Example two

Fig. 2 is a schematic structural diagram of an integrated system for page applications according to a second embodiment of the present invention. The present embodiment is optimized based on the technical solution provided in the foregoing embodiment. Referring to fig. 2, the integration system 20 of the page application may include a common services layer 240 in addition to an access entry layer 210, a container management layer 220, and a page presentation layer 230.

Wherein the access entry layer 210, the container management layer 220, and the page presentation layer 230 have the same functions and effects as those of the access entry layer, the container management layer, and the page presentation layer provided in the above embodiments, and the common service layer 240 provides a unified login service, a registration service, and a navigation service for different page applications.

Specifically, since a large number of page applications are integrated in the integrated system 20 and each page application needs to be logged in before access, the embodiment sets a corresponding unified login service for each page application in the integrated system 20 through the public service layer 240, and after entering the integrated system 20, a user can log in the integrated system 20 through the unified login service, and does not need to log in each page application in the integrated system 20, so that multiple logins of the same user on different page applications are avoided.

Meanwhile, in order to clearly define each page application accessed in the integrated system 20, after the container management layer 220 packages the corresponding page application through different containers under the container management layer, the embodiment may also register each accessed page application on the public service layer 240 by adopting a corresponding registration service, that is, register basic information of each accessed page application on the public service layer 240, and manage functions such as disabling and deleting the page application, where when the main routing module in the access entry layer 210 determines the target container management component in the container management layer 220 according to the access address of the application to be accessed, the preset address container mapping mechanism may be set through the registration service on the public service layer 240.

Alternatively, the common services layer 240 may maintain link management between various page applications accessed in the integrated system 20 through navigation services, such as implementing navigation services between different page applications through menus or quick links.

It should be noted that, since the user needs to trigger and execute different services provided by the common service layer 240 for different page applications on the front end interface of the integrated system 20, the page display layer 230 is provided with service entries under different services in the common service layer 240 in the front end interface, so that the user triggers and executes different services.

Further, since the page applications accessed by the integrated system 20 include two types of multi-page applications (Multiple Page Application, MPA) and single-page applications (Single Page Application, SPA), and MPA application refers to that the whole Web application is composed of multiple pages, and the content switching is mainly implemented by switching different pages, this implementation requires that the common code be rerun each time because each page is reloaded; the SPA application refers to that only one page exists in the whole Web application, the content switching is completed by updating a designated area in the page, the common implementation mode is that page addresses are mapped to virtual pages (containing the content to be updated), and then the loading and the replacement of the virtual page content are triggered by monitoring the change of the page addresses, so that the reloading operation of a common code and the re-rendering of unchanged content are reduced to the greatest extent; meanwhile, a certain class of SPA applications may have more intrusion into the running environment, so in order to avoid context conflict between different page applications, the container management layer 220 of this embodiment may set, according to the context isolation state of each page application, that the lower container may include three types of non-embedded single application containers (SPAContainer), embedded single application containers (iframe appcontainer) and shared embedded application containers (sharedIframe appcontainer), where, since a single page application has only one page, there is a switching of multiple pages in multiple page applications, the container management layer 220 packages the single page application in the context isolation running through the non-embedded single application container, packages the single page application in the context non-isolation running through the embedded single application container, and the shared embedded application container is used for packaging multiple page applications, where the embedded single application container can ensure that the service will not have context conflict with other applications in the running process, that is isolated from the context of the other applications in the single page application with more intrusion into the running environment, and ensures the success rate of executing the single page application.

It should be noted that, in this embodiment, since the non-embedded single application container and the embedded single application container are both used for packaging single page applications and switch within one page, it may be set that only one single page application is packaged in one non-embedded single application container, only one single page application is packaged in one embedded single application container, at least one multi-page application is packaged in one shared embedded application container, and only one packaged multi-page application is loaded in one shared embedded application container at each time.

At this time, a special web page element < iframe > is adopted in the embedded single application container and the shared embedded application container to load another corresponding embedded page application in the internal area of one page, at this time, the page where the < iframe > is located is a main page, and the page loaded by the < iframe > is the embedded page of the page application packaged by the container. Specifically, the shared embedded application container loads multiple multi-page applications sharing one < iframe >, but only one at a time.

In this embodiment, for the containers under different types set in the container management layer 220, the non-embedded container and the embedded container may be managed by the first container management component 221 and the second container management component 222, respectively, where the first container management component 221 is used to manage the non-embedded single application container, and the second container management component 222 is used to manage the embedded single application container and the shared embedded application container; while a first container management component 221 can manage a plurality of non-embedded single application containers for different numbers of page applications supported by the containers, and a second container management component 222 can manage a plurality of embedded single application containers and a shared embedded application container, thereby managing all page applications accessed by the integrated system 20.

Illustratively, embedded single application containers and non-embedded single application containers are managed (e.g., displayed and hidden) and responsive to routing events (e.g., page access events) by corresponding second container management component 222 and first container management component 221; the second container management component 222 can also implement automatic reclamation of the managed embedded single application container (e.g., by marking access times, most accesses and most recently accessed non-reclamation, access times few and very long non-accessed reclamation) to optimize performance issues caused by coexistence of multiple < iframe > elements.

In addition, in order to enable the container in the container management layer 220 to accurately analyze the access content of the packaged container under the page application implemented by adopting the corresponding technical scheme, in this embodiment, the non-embedded single application container may be configured with an application adapter under a non-embedded type, the embedded single application container may be configured with a home page communicator corresponding to a single page application, the shared embedded application container may be configured with a home page communicator corresponding to a multi-page application, the single application embedded page under the single application container may be configured with an embedded page communicator corresponding to a single page application and an application adapter under an embedded type, and the multi-application embedded page under the shared embedded application container may be configured with an embedded page communicator corresponding to a multi-page application and an application adapter under an embedded type.

Specifically, the non-embedded single application container can be accessed by an application adapter under a non-embedded type, and the embedded single application container and the shared embedded application container can be used for respectively accessing the access address of the page application packaged by the container through the application adapter under the loading embedded type on the corresponding embedded page, so that the corresponding access content is obtained through analysis, and the limitation caused by the implementation technology adopted by the page application is avoided.

Meanwhile, when a user accesses a page application corresponding to package on the embedded single application container and the shared embedded application container in this embodiment, since the page application is embedded in a main page of the integrated system 20, at this time, corresponding access interaction exists between the main page and an embedded page of the page application, at this time, the embedded single application container and the shared embedded application container may perform access interaction on an application to be accessed through a pre-configured main page communicator and an embedded page communicator on an embedded page under the container.

For example, when a single page application embedded in a single application container is to interact with a main page of the integrated system 20, the main page communicator and the embedded page communicator need to be relied on to communicate, and at this time, asynchronous communication based on a browser postMessage method is adopted, and each access is ensured to be successfully arrived by relying on an access identifier and a handshake message of an application to be accessed; whereas single page applications that are not embedded in a single application container rely on new application adapters to interface with single page applications implemented by different technologies (e.g., single page applications implemented by front end frame Vue need to implement vuespadapter, and single page applications implemented by front end frame act need to implement reactispaadapter).

According to the technical scheme provided by the embodiment, the first container management component, the second container management component, the non-embedded single application container, the embedded single application container and the shared embedded application container are arranged in the container management layer, the first container management component manages the non-embedded single application container, the second container management component manages the embedded single application container and the shared embedded application container, the non-embedded single application container packages single page applications under the context isolation operation, the embedded single application container packages single page applications under the context non-isolation operation, the shared embedded application container packages multi-page applications, various page applications are integrated in a containerization mode, the same technical scheme is not required to be adopted to achieve different page applications or page applications are only accessed in an integrated system in an internal embedded mode, the application access under different integrated modes is achieved by adaptively increasing the containers in the integrated system to package the page applications under different types, the safety and the diversity of application integration are guaranteed, and simultaneously the page display layer sets corresponding front-end interface areas for the different containers, so that the access content of the application to be accessed is directly loaded, and the time consumption of the application and the access is reduced.

Example III

Fig. 3 is a flowchart of an application access method according to a third embodiment of the present invention. The embodiment can be applied to the page application integrated system provided by any embodiment, and a specific access process of any page application in the integrated system is mainly described.

Optionally, referring to fig. 3, the present embodiment may mainly include the following steps:

s310, determining a corresponding target container management component of the application to be accessed in the container management layer through the access entry layer according to the access address of the application to be accessed.

Specifically, the page application in the embodiment may refer to a developed web application running on a web browser, where the web application may be directly started in the web browser without being installed and updated on a terminal by a user, and corresponding application content may be loaded as required; because of the large amount of development of web applications, each web application related to the service needs to be integrated into a large-scale web application system, so that users can use more easily and manage conveniently, the embodiment realizes the access functions under different page applications through the integrated system integrated with a plurality of page applications, and the integrated system is specifically designed into four layers of a public service layer, an access entrance layer, a container management layer and a page display layer aiming at different types of the access functions.

Optionally, the user may access different applications accessed by the integrated system through the navigation service provided by the public service layer, and take charge of data and function initialization of the integrated system through the access entry layer, and monitor address changes of corresponding browsers when the user triggers access to different applications in a front end interface of the integrated system, so as to determine an application to be accessed in this time, further receive an access address of the application to be accessed through the main routing module, and find a target container management component corresponding to the access address in the container management layer, so that the access function of the application to be accessed is processed through the target management component subsequently.

S320, searching out a target container which is packed with the application to be accessed through the target container management component, and determining the access content of the application to be accessed according to the access address through the target container.

Optionally, in order to perform classification management under different context isolation states on each page application implemented by adopting different technical schemes, a container management layer in the integrated system may set corresponding containers for the context isolation states of each page application to package each page application, so that the page application is accessed into the integrated system in the embodiment, and the container management layer manages the containers of the corresponding page applications through corresponding container management components; therefore, after the target container management component corresponding to the access address of the application to be accessed is found, the target container in which the application to be accessed is packaged can be directly found out from all containers managed under the target container management component through the target container management component, and then the corresponding page access address in the access address of the application to be accessed is driven through the target container, so that the access content of the application to be accessed is determined.

S330, displaying the access content in the front end interface area corresponding to the target container through the page display layer.

Optionally, the page display layer in this embodiment is mainly responsible for corresponding display in the front end interface on the integrated system, at this time, the page display layer sets different containers in the container management layer, and after packaging corresponding page applications, different interface tags may be used to set corresponding front end interface areas for the page applications packaged by each container in the front end interface, so after determining the access content of the application to be accessed through the target container, the access content of the application to be accessed may be directly displayed in the front end interface areas corresponding to the target container through the page display layer, thereby implementing access of different page applications.

In this embodiment, since the page applications accessed in the integrated system include single-page applications and multiple-page applications, and a certain class of single-page applications may have more intrusion into the running environment, so in order to avoid context conflicts between different page applications, the container management layer in this embodiment may set the lower container according to the context isolation state of each page application to include three types of non-embedded single-application containers, embedded single-application containers and shared embedded application containers, where, because there is only one page in the single-page application, multiple pages are switched in the multiple-page application, the container management layer packages the single-page applications under the context isolation running through the non-embedded single-application containers, the embedded single-application containers are used to package the multiple-page applications, and the embedded single-application containers can ensure that the service cannot have context conflicts with other applications in the running process, that is, the context in the single-page application with more intrusion into the running environment is isolated from the context of other page applications, and ensure the success rate of executing the single-page applications.

At this time, when a user accesses a single-page application packaged by an embedded single-application container or a multi-page application packaged by a shared embedded application container, interaction between an embedded page of the single-page application or the multi-page application and a main page of an integrated system is required, and in this embodiment, the accessed content is displayed in a front end interface area corresponding to a target container through a page display layer, which may specifically include: if the target container is a non-embedded single-application container, directly displaying the access content in a front end interface area corresponding to the target container through the page display layer; if the target container is an embedded single application container or a shared embedded application container, transmitting an access notification of an application to be accessed through a main page communicator under the target container and an embedded page communicator on an embedded page under the target container, and displaying access contents in the embedded page of the target container through a page display layer after receiving a corresponding access success instruction through the target container.

For example, if the target container is a non-embedded single-application container, after determining the access content of the application to be accessed according to the access address by the target container, the target container may directly notify the page display layer to display the access content in the front end interface area corresponding to the target container; if the target container is an embedded single application container or a shared embedded application container, after the access content of the application to be accessed is determined according to the access address through the target container, interaction is needed between a main page of the integrated system and an embedded page of the application to be accessed, at this time, the target container firstly sends an access notification of the application to be accessed to a main page communicator which controls the access of the main page under the target container, the main page communicator sends the access notification of the application to be accessed to the embedded page communicator which controls the access of the embedded page under the target container in an asynchronous message communication mode, the embedded page communicator processes the access notification of the application to be accessed in the embedded page, and after the embedded page is accessed successfully, a corresponding access success instruction is returned to the target container according to the embedded page communicator and the main page communicator in the original path, and after the target container receives the corresponding access success instruction, the page display layer is notified to display the access content of the application to be accessed in the embedded page of the target container.

Example IV

Fig. 4 is a flowchart of an application access method according to a fourth embodiment of the present invention. The embodiment can be applied to the integrated system of the page application provided by any embodiment, and mainly describes other processes existing in the access process of the page application. Referring to fig. 4, the present embodiment may mainly include the following steps:

s410, registering the page application packaged by different containers in the container management layer in the integrated system through the public service layer, and generating a mapping address mechanism between the page application and the containers.

Optionally, in this embodiment, the common service layer provides a unified login service, a registration service and a navigation service for different page applications. Because a large number of page applications are integrated in the integrated system, and each page application needs to be logged in before being accessed, the embodiment sets corresponding unified login service for each page application in the integrated system through the public service layer, and after entering the integrated system, a user can log in the integrated system through the unified login service without logging in each page application in the integrated system, so that multiple logins of the same user on different page applications are avoided. Meanwhile, in order to clearly define each page application accessed in the integrated system, after the container management layer packages the corresponding page application through different containers below the container management layer, the embodiment can also register each accessed page application on the public service layer by adopting corresponding registration service, namely, registering basic information of each accessed page application on the public service layer, managing functions such as disabling and deleting the page application, and the like, and further registering the page application packaged through different containers in the container management layer in the integrated system through the public service layer, so as to generate an address container mapping mechanism between each accessed page application and a corresponding container management component in the integrated system, thereby searching the corresponding target container management component when the subsequent page application accesses.

S420, determining an access address of the application to be accessed, which is designated by the application switching operation, through the page presentation layer.

In particular, the common service layer can maintain link management between various page applications accessed in the integrated system through navigation service, such as realizing navigation service between different page applications through menu or shortcut link. At this time, because the user needs to trigger and execute different services provided by the public service layer for different page applications on the front end interface of the integrated system, the page display layer is provided with service inlets under different services in the public service layer in the front end interface so as to trigger and execute different services by the user, therefore, the page display layer in the embodiment can provide switching inlets of access contents under different page applications on the front end interface besides setting front end interface areas of corresponding access contents displayed by each page application, at this time, the page display layer presets switching display of the access contents under different containers in the front end interface in the container management layer, that is, a navigation schematic diagram of the different page applications is set on the front end interface, the user selects the application to be accessed in the navigation schematic diagram, and then determines the access address of the application to be accessed specified by the application switching operation through the navigation control element set on the page display layer; by way of example, the navigation control element may be a tab navigation button or menu item in the front-end interface, or the like.

S430, determining a target container management component corresponding to the access address of the application to be accessed by the access entry layer through a mapping address mechanism.

Specifically, after the access entry layer receives the access address of the application to be accessed, the main routing module under the access entry layer monitors the access address of the application to be accessed at the current moment, namely the corresponding browser address, so that the target container management component corresponding to the application to be accessed is determined according to the matching condition between the access address and the container management component in the preset mapping address mechanism, and the target container management component is directly adopted for carrying out access processing on the application to be accessed.

S440, searching out a target container which is packed with the application to be accessed through the target container management component, and determining the access content of the application to be accessed according to the access address through the target container.

S450, displaying the access content in the front end interface area corresponding to the target container through the page display layer.

According to the technical scheme provided by the embodiment, various page applications are integrated in a containerized mode, the same technical scheme is not required to be adopted to realize different page applications or page applications are only accessed in an integrated system in an internal embedding mode, the application access in different integrated modes is realized by adaptively adding containers to package page applications in different external types in the integrated system, the safety and diversity of application integration are ensured, and meanwhile, a page display layer sets corresponding front-end interface areas for different containers, so that the access content of applications to be accessed is directly loaded, and the time consumption of application integration and access is reduced.

Example five

Fig. 5 is a schematic structural diagram of an application access device provided in a fifth embodiment of the present invention, which is configured in the integrated system of a page application according to any embodiment of the present invention, and specifically, as shown in fig. 5, the device may include:

the container component determining module 510 is configured to determine, through the access entry layer, a target container management component corresponding to the application to be accessed in the container management layer according to the access address of the application to be accessed;

the access content determining module 520 is configured to find a target container that packages the application to be accessed through the target container management component, and determine access content of the application to be accessed according to the access address through the target container;

the access content display module 530 is configured to display, through the page display layer, the access content in a front end interface area corresponding to the target container.

Further, the application access device may further include:

and the application registration module is used for registering the page application packaged by different containers in the container management layer in the integrated system through the public service layer and generating a mapping address mechanism between the page application and the containers.

Further, the container assembly determining module 510 may be specifically configured to:

and determining a target container management component corresponding to the access address by adopting a mapping address mechanism through the access entry layer.

Further, the application access device may further include:

and the application switching module is used for determining the access address of the application to be accessed, which is designated by the application switching operation, through the page display layer.

Further, the above-mentioned access content presentation module 530 may be specifically configured to:

if the target container is a non-embedded single-application container, directly displaying the access content in a front end interface area corresponding to the target container through the page display layer;

if the target container is an embedded single application container or a shared embedded application container, transmitting an access notification of an application to be accessed through a main page communicator under the target container and an embedded page communicator on an embedded page under the target container, and displaying access contents in the embedded page of the target container through a page display layer after receiving a corresponding access success instruction through the target container.

The application access device provided by the embodiment is applicable to the application access method provided by any embodiment, and has corresponding functions and beneficial effects.

Example six

Fig. 6 is a schematic structural diagram of an apparatus according to a sixth embodiment of the present invention, and as shown in fig. 6, the apparatus includes a processor 60, a storage device 61, and a communication device 62; the number of processors 60 in the device may be one or more, one processor 60 being taken as an example in fig. 6; the processor 60, the storage means 61 and the communication means 62 in the device may be connected by a bus or other means, in fig. 6 by way of example.

The storage device 61 is a computer readable storage medium, and may be used to store a software program, a computer executable program, and a module, such as program instructions/modules corresponding to the application access method according to any embodiment of the present invention. The processor 60 executes various functional applications of the device and data processing, i.e., implements the above-described application access method, by running software programs, instructions, and modules stored in the storage 61.

The storage device 61 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for functions; the storage data area may store data created according to the use of the terminal, etc. Further, the storage 61 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, the storage 61 may further include memory remotely located with respect to the processor 60, which may be connected to the device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The communication means 62 may be used to enable a network connection or a mobile data connection between the devices.

The device provided by the embodiment can be used for executing the application access method provided by any embodiment, and has corresponding functions and beneficial effects.

Example seven

The seventh embodiment of the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the application access method in any of the above embodiments. The method specifically comprises the following steps:

Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present invention is not limited to the method operations described above, and may also perform the related operations in the application access method provided in any embodiment of the present invention.

From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product, which may be stored in a computer readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, etc., and include several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments of the present invention.

It should be noted that, in the above embodiment of the application access device, each unit and module included are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.

The above description is only of the preferred embodiments of the present invention and is not intended to limit the present invention, and various modifications and variations may be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. An integrated system for a page application, comprising: accessing an entry layer, a container management layer and a page display layer; wherein,

the access entry layer determines a target container management component in the container management layer according to an access address of an application to be accessed; the container management layer searches a target container packed with the application to be accessed through the target container management component, and determines the access content of the application to be accessed through the target container; the page display layer displays the access content in a front end interface area corresponding to the target container;

the container management layer sets the corresponding target containers for the context isolation states of the applications to be accessed respectively; the container management layer comprises a first container management component, a second container management component, a non-embedded single application container, an embedded single application container and a shared embedded application container, wherein the first container management component is used for managing the non-embedded single application container, and the second container management component is used for managing the embedded single application container and the shared embedded application container; the non-embedded single application container is used for packaging single page applications under the context isolation operation, the embedded single application container is used for packaging single page applications under the context non-isolation operation, and the shared embedded application container is used for packaging multi-page applications.

2. The integrated system of claim 1, further comprising a common service layer that provides unified login, registration, and navigation services for different page applications.

3. The integrated system of claim 2, wherein the page presentation layer is provided with service portals under different services in the common service layer in a front-end interface.

4. The integrated system of claim 1, wherein the access entry layer includes an initialization module for controlling function initialization of the integrated system under different hierarchies, and a main routing module for monitoring access addresses of applications to be accessed and determining target container management components corresponding to the applications to be accessed using a mapping address mechanism.

5. The integrated system of claim 1, wherein only one single-page application is wrapped in a non-embedded single-application container, only one single-page application is wrapped in an embedded single-application container, at least one multi-page application is wrapped in a shared embedded application container, and the shared embedded application container only loads one wrapped multi-page application at each time.

6. The integrated system of claim 1, wherein the non-embedded single application container is configured with an application adapter under a non-embedded type, the embedded single application container is configured with a main page communicator corresponding to a single page application, the shared embedded application container is configured with a main page communicator corresponding to a multi-page application, the embedded single application embedded page under the embedded single application container is configured with an embedded page communicator corresponding to a single page application and an application adapter under an embedded type, and the multi-application embedded page under the shared embedded application container is configured with an embedded page communicator corresponding to a multi-page application and an application adapter under an embedded type.

7. The integrated system of claim 1, wherein each container in the container management layer has a corresponding container interface disposed thereon, the container interface having defined therein application properties and functional methods supported by the container.

8. The integrated system of claim 1, wherein the page presentation layer sets access content under different containers in the container management layer to switch presentation in a front end interface.

9. The integrated system of claim 8, wherein a navigation control element is provided on the page presentation layer for controlling switching of applications to be accessed under different containers.

10. An application access method, which is applied to the integrated system of the page application of any one of claims 1 to 9, and comprises the following steps:

searching a target container which packages the application to be accessed through the target container management component, and determining access content of the application to be accessed according to the access address through the target container; the container management layer sets the corresponding target containers for the context isolation states of the applications to be accessed respectively; the container management layer comprises a first container management component, a second container management component, a non-embedded single application container, an embedded single application container and a shared embedded application container, wherein the first container management component is used for managing the non-embedded single application container, and the second container management component is used for managing the embedded single application container and the shared embedded application container; the non-embedded single application container is used for packaging single page applications under the context isolation operation, the embedded single application container is used for packaging single page applications under the context non-isolation operation, and the shared embedded application container is used for packaging multi-page applications;

11. The method of claim 10, further comprising, prior to determining, by the access entry layer, a corresponding target container management component of the application to be accessed in the container management layer based on the access address of the application to be accessed:

and registering the page application packaged by different containers in the container management layer in the integrated system through the public service layer, and generating a mapping address mechanism between the page application and the containers.

12. The method according to claim 11, wherein determining, by the access portal layer, a corresponding target container management component of the application to be accessed in the container management layer according to the access address of the application to be accessed, comprises:

and determining a target container management component corresponding to the access address by the access entry layer through adopting the mapping address mechanism.

13. The method of claim 10, further comprising, prior to determining, by the access entry layer, a corresponding target container management component of the application to be accessed in the container management layer based on the access address of the application to be accessed:

And determining the access address of the application to be accessed, which is designated by the application switching operation, through the page presentation layer.

14. The method of claim 10, wherein displaying the access content in the front-end interface region corresponding to the target container through a page display layer comprises:

if the target container is a non-embedded single-application container, the access content is displayed in a front end interface area corresponding to the target container directly through a page display layer;

and if the target container is an embedded single application container or a shared embedded application container, transmitting the access notification of the application to be accessed through a main page communicator under the target container and an embedded page communicator on an embedded page under the target container, and displaying the access content in the embedded page of the target container through a page display layer after receiving a corresponding access success instruction through the target container.

15. An application access device, configured in the integrated system of the page application of any one of claims 1 to 9, comprising:

The access content determining module is used for searching out a target container which is packed with the application to be accessed through the target container management component, and determining the access content of the application to be accessed according to the access address through the target container; the container management layer sets the corresponding target containers for the context isolation states of the applications to be accessed respectively; the container management layer comprises a first container management component, a second container management component, a non-embedded single application container, an embedded single application container and a shared embedded application container, wherein the first container management component is used for managing the non-embedded single application container, and the second container management component is used for managing the embedded single application container and the shared embedded application container; the non-embedded single application container is used for packaging single page applications under the context isolation operation, the embedded single application container is used for packaging single page applications under the context non-isolation operation, and the shared embedded application container is used for packaging multi-page applications;

16. An apparatus for application access, the apparatus comprising:

one or more processors;

a storage means for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the application access method of any of claims 10-14.

17. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the application access method according to any of claims 10-14.