CN113127010A - Application management method and device, electronic equipment and storage medium - Google Patents

Application management method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113127010A
CN113127010A CN201911414874.0A CN201911414874A CN113127010A CN 113127010 A CN113127010 A CN 113127010A CN 201911414874 A CN201911414874 A CN 201911414874A CN 113127010 A CN113127010 A CN 113127010A
Authority
CN
China
Prior art keywords
target application
global variable
application
markup language
hypertext markup
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201911414874.0A
Other languages
Chinese (zh)
Other versions
CN113127010B (en
Inventor
陈毅飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Intellifusion Technologies Co Ltd
Original Assignee
Shenzhen Intellifusion Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Intellifusion Technologies Co Ltd filed Critical Shenzhen Intellifusion Technologies Co Ltd
Priority to CN201911414874.0A priority Critical patent/CN113127010B/en
Publication of CN113127010A publication Critical patent/CN113127010A/en
Application granted granted Critical
Publication of CN113127010B publication Critical patent/CN113127010B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/62Uninstallation

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the invention provides an application management method, an application management device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining the first global variable as a current global variable so as to mount the first target application; when the first target application is unloaded, the first global variable is changed into a second global variable so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application. The invention can effectively reduce the interference of each target application in the using process and is convenient for management.

Description

Application management method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of application management technologies, and in particular, to an application management method and apparatus, an electronic device, and a storage medium.
Background
Currently, front-end engineering of many background management systems is based on SPA (Single Page Application) Application of a certain front-end framework, and has a large defect in the following Application scenarios: 1. a plurality of applications are integrated into one application, namely the applications of different frames can only be reconstructed and unified into one frame, the development time is huge, and all reconstructed functional details need secondary detailed tests. 2. The development of a large application needs to unify the use frames of all developers, and the frame may not be available for supporting staff or newly recruited staff of a cross-technical department, so that the lead time and cost of learning, training and the like are brought, and the project development time is prolonged. When applications developed by a plurality of different frameworks are integrated into one application, the above-mentioned defects can be solved, but in the existing integration technology, after the applications developed by the plurality of different frameworks are integrated into one application, interference exists between the applications in the using process and the management is inconvenient.
Disclosure of Invention
The embodiment of the invention provides an application management method, which can effectively reduce the interference of each target application in the use process and is convenient to manage.
In a first aspect, an embodiment of the present invention provides an application management method, including:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining the first global variable as a current global variable so as to mount the first target application;
when the first target application is unloaded, the first global variable is changed into a second global variable so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application.
Preferably, the method further comprises:
presetting the corresponding first preset sandbox for the first target application, wherein the first preset sandbox is used for storing the first global variable;
and presetting a corresponding second preset sandbox for the second target application, wherein the second preset sandbox is used for storing the second global variable.
Preferably, before the step of changing the first global variable into a second global variable when the first target application is uninstalled, so as to mount a second target application corresponding to the second global variable, the method includes:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting information comprises second target application information corresponding to the second target application;
when the second mounting request information is received, returning the first global variable to the first preset sandbox for storage so as to unload the first target application;
and extracting the second global variable from the second preset sandbox according to the second target application information.
Preferably, before the determining the first global variable as the current global variable to mount the first target application, the method further includes the following steps:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
Preferably, before the changing the first global variable into a second global variable to mount a second target application corresponding to the second global variable, the method further includes the following steps:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Preferably, the method further comprises the steps of:
setting the corresponding first hypertext markup language and the first style corresponding to the first hypertext markup language for the first target application in advance, and storing the first hypertext markup language and the first style;
and setting the corresponding second hypertext markup language and the second style corresponding to the second hypertext markup language for the second target application in advance, and storing the second hypertext markup language and the second style.
In a second aspect, an embodiment of the present invention further provides an application management apparatus, where the application management apparatus includes:
the system comprises a first obtaining module, a second obtaining module and a first loading module, wherein the first obtaining module is used for obtaining first loading request information for loading a first target application, and the first loading request information carries first target application information corresponding to the first target application;
the first extraction module is used for extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
the first mounting module is used for determining the first global variable as a current global variable so as to mount the first target application;
and the second mounting module is used for changing the first global variable into a second global variable when the first target application is unloaded so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application.
Preferably, the application management apparatus further includes:
a first preset module, configured to set a corresponding first preset sandbox for the first target application in advance, where the first preset sandbox is used to store the first global variable;
and the second preset module is used for setting a corresponding second preset sandbox for the second target application in advance, and the second preset sandbox is used for storing the second global variable.
In a third aspect, an embodiment of the present invention further provides an electronic device, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the application management method provided in the above embodiments when executing the computer program.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when being executed by a processor, the computer program implements the steps in the application management method provided in the foregoing embodiment.
In the embodiment of the invention, first mounting request information for mounting a first target application is obtained, wherein the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining the first global variable as a current global variable so as to mount the first target application; when the first target application is unloaded, the first global variable is changed into a second global variable so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application. Each target application is provided with a sandbox used for storing corresponding global variables, and the corresponding global variables can be extracted from the sandbox for use when the target application is mounted. When another target application needs to be mounted, the global variable of the currently mounted target application is directly replaced by another global variable corresponding to the other target application, and then free switching between the two target applications can be achieved. In the process of switching two different global variables, interference does not exist between the global variables, and mounting and unloading of the other party are not affected. And then can effectively reduce the interference of each target application in the use process and be convenient for management.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a system architecture diagram provided by an embodiment of the present invention;
fig. 2 is a flowchart of an application management method according to an embodiment of the present invention;
FIG. 3 is a flow chart of another application management method provided by the embodiment of the invention;
FIG. 4 is a flowchart of another application management method provided in an embodiment of the present invention;
FIG. 5 is a flow chart of another application management method provided by the embodiment of the invention;
fig. 6 is a schematic structural diagram of an application management apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of another application management apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another application management apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of another application management apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
To explain the technical solution of the present invention more clearly, as shown in fig. 1, fig. 1 is a system architecture diagram provided by an embodiment of the present invention, and the system architecture 100 may include a browser 101; a host application 102; a first target application 103, a second target application 104 integrated in the main application 102; a first service 105 corresponding to the first target application 103; and a second service 106 corresponding to the second target application 104. The main application 102 is configured to implement switching and management between the first target application 103 and the second target application 104 according to the request information sent by the browser 101, and a user may access the first service 105 and the second service 106 provided by the first target application 103 and the second target application 104 through the browser 101.
The first target application 103 and the second target application 104 may be provided in various electronic devices or terminals having a display screen and supporting web browsing, including, but not limited to, a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), a laptop portable computer, a desktop computer, and the like. The first service 105 and the second service 106 may be provided in servers corresponding to electronic devices or terminals where the first target application 103 and the second target application 104 are located. Various communication client applications, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, a management application, and the like, may be installed in the electronic device or the terminal.
It should be noted that the application management method provided in the embodiment of the present application is generally executed by the host application 102, and accordingly, the application management apparatus is equivalent to the host application 102.
It should be understood that browser 101 in FIG. 1; a host application 102; a first target application 103 and a second target application 104 integrated in the main application 102; the number of first services 105 corresponding to the first target application 103 and the number of second services 106 corresponding to the second target application 104 are merely illustrative. There may be any number of browsers 101, as desired for implementation; a host application 102; a first target application 103 and a second target application 104 integrated in the main application 102; a first service 105 corresponding to the first target application 103 and a second service 106 corresponding to the second target application 104. Generally, one target application corresponds to one service, that is, the target application corresponds to the service provided by the target application one to one.
It should be noted that the application management apparatus, the first target application 103, and the second target application 104 mentioned in the following embodiments may all correspond to the master application 102, the first target application 103, and the second target application 104 in fig. 1.
In the following embodiments, the first target application 103 is an application that the user currently wants to access, and the second target application 104 is an application that the user wants to access next, and in order to distinguish access to different applications, the two different applications are referred to as the first target application 103 and the second target application 104, respectively. However, if three different applications are accessed in sequence, the first accessed application is referred to as a first target application 103, the second accessed application is referred to as a second target application 104, the third accessed application is referred to as a third target application, and so on, and if multiple applications are accessed in sequence, the naming can be performed in sequence. The first target application 103, the second target application 104 and the third target application may be replaced with each other. The first target application 103 and the second target application 104 may be directly used to replace two different target applications, and therefore, the names of the target applications are not limited.
Referring to fig. 2, fig. 2 is a flowchart of an application management method according to an embodiment of the present invention, and as shown in fig. 2, the method includes the following steps:
step 201, obtaining first mounting request information for mounting a first target application, where the first mounting request information carries first target application information corresponding to the first target application.
When an application is mounted, the application can be accessed by other users and uses the service of the application. It can also be said that the application can provide the service normally. The first target application may be an application that the user is currently accessing by the user. The first mounting request information is used for requesting the mounting of the request information of the first target application. The first target application information may include routing information, identification information, and the like of the first target application.
Specifically, when a user wants to access a service of a first target application, the user may edit first mount request information for mounting the first target application through a browser and send the first mount request information to a host application, and at this time, the host application may receive the first mount request information. After the main application receives the first mount request message, it can know which application service the user wants to access according to the first target application message, and step 102 can be executed subsequently.
Step 202, extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information.
The sandbox is a region created in the main application to store global variables used by different target applications, and the sandbox is provided with identifiers corresponding to the target applications. The first preset sandbox is preset, specifically, before step 201, a corresponding first preset sandbox is preset for the first target application, where the first preset sandbox carries an identifier of the first target application. The first preset sandbox is used for storing a first global variable. The first global variable is a global variable used by the first target application in the implementation process. The first global variable is also preset. The global variable can be created by some object function of some application, or can be created anywhere in the application program. The global variable is a variable that can be referenced by all objects or functions of the application. To this end, each application is provided with its own global variable, and each global variable may be provided with its own name, for example, the global variable used in the first target application may be represented by a, b, c and/or d, etc., and the first global variable may contain one or more variables. Of course, each application also sets its own local variables (which may be referred to as run variables), which may also be referred to as internal variables, relative to global variables. Variables created by an object or a function of an application are usually local variables, which can only be internally referenced, but cannot be referenced by other objects or functions.
Specifically, after the main application receives the first mount request information, the target application that the user specifically wants to access may be determined according to the routing information or the identification information in the first target application information carried in the first mount request information, that is, the target application that the user wants to access is determined to be the first target application, for example, the routing information of the first target application is route 1, and when the first mount request information carries the routing information of route 1, it may be known that the user wants to access the first target application. At this time, the first target application should be mounted, that is, the first global variable of the first target application is extracted from the first preset sandbox corresponding to the first target application.
And step 203, determining the first global variable as the current global variable so as to mount the first target application.
The current global variable is a global variable being mounted on the global, and may also be a global variable corresponding to a target application being mounted.
Specifically, to mount the first target application, it is only necessary to mount the corresponding first global variable on the global to become the current variable. For example, if a second target application is mounted, mounting a second global variable corresponding to the second target application on the global to become the current global variable may be implemented. If other target applications are in the mount state before, the global variable which is mounted on the global before the target application which is mounted can be replaced.
And 204, when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable.
The uninstalling may refer to that the target application is not accessed, and the target application is downloaded to the offline. The second preset sandbox is preset, and the second global variable is stored in the second preset sandbox corresponding to the second target application. Specifically, before step 201, a corresponding second preset sandbox is preset for the second target application, where the second preset sandbox carries an identifier of the second target application. The second preset sandbox is used for storing a second global variable. The second global variable is a global variable used by the second target application in the implementation process. The second global variable is also preset, and the second global variable may contain one or more variables.
Specifically, in step 203, the first target application is mounted, and when a user wants to access a service of the second target application, the main application needs to switch the first target application being mounted to the second target application for mounting, and at this time, the first target application needs to be uninstalled and the second application needs to be mounted at the same time. Therefore, the second target application can be mounted only by replacing the second global variable corresponding to the second target application with the first global variable which is being mounted on the global.
It should be noted that, in the prior art, each target application has its own global variable, and when the number of target applications is multiple, or multiple target applications are developed in the same manner, or multiple target applications are developed by the same developer, it is inevitable to use the same identifier, such as the same letter or symbol, when naming the global variable of each target application. When each target application is used individually, there is no influence, but once a plurality of target applications are used in an integrated manner, global variable interference exists between global variables of each target application when the plurality of target applications are used due to the fact that names of the global variables are the same, and the like.
In the embodiment of the invention, first mounting request information for mounting a first target application is obtained, wherein the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining a first global variable as a current global variable so as to mount a first target application; and when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application. Each target application is provided with a sandbox used for storing corresponding global variables, and the corresponding global variables can be extracted from the sandbox for use when the target application is mounted. When another target application needs to be mounted, the global variable of the currently mounted target application is directly replaced by another global variable corresponding to the other target application, and then free switching between the two target applications can be achieved. In the process of switching two different global variables, interference does not exist between the global variables, and mounting and unloading of the other party are not affected. And then can effectively reduce the interference of each target application in the use process and be convenient for management.
Optionally, referring to fig. 3 and fig. 3, which are flowcharts of another application management method provided by the embodiment of the present invention, on the basis of fig. 2, before step 104, the application management method further includes the steps of:
step 301, determining whether second mount request information for mounting a second target application is received, where the second mount information includes second target application information corresponding to the second target application.
Step 302, when the second mount request information is received, returning the first global variable to the first preset sandbox for storage, so as to unload the first target application.
And 303, extracting a second global variable from a second preset sandbox according to the second target application information.
The second mount request information is used for requesting to mount request information of a second target application. The second target application information may include routing information identification information of the second target application, and the like.
Specifically, during the mount of the first target application, if the primary application receives the second mount request information, the target application to be specifically accessed by the user may be determined according to the routing information, the identification information, or the like in the second target application information carried in the second mount request information, that is, the target application to be accessed by the user is determined to be the second target application, for example, the routing information of the second target application is route 2, and when the second mount request information carries the routing information of route 2, the user may know that the user wants to access the second target application. At this time, the first target application needs to be unloaded first, and the first global variable corresponding to the first target application is unloaded from the global and returned to the corresponding first preset sandbox for storage, so that when the first target application is mounted next time, the corresponding first global variable can be extracted from the first preset sandbox again, and the first target application is mounted again.
When the first target application is unloaded, the corresponding second global variable is extracted from the second preset sandbox corresponding to the second target application, so that the second global variable is hung on the whole to be changed into the current global variable conveniently, the hanging of the second target application is realized, and the user access is facilitated.
It should be noted that, when the second target application is unloaded, the corresponding second global variable may also be returned from the global state to the corresponding second preset sandbox for storage, so that when the second target application is mounted next time, the corresponding second global variable may be extracted from the second preset sandbox again, and the second target application is mounted again.
In the embodiment of the invention, the alternate mounting between two different target applications can be realized, and when each target application is unloaded, the corresponding global variable can be returned to the corresponding preset sandbox for storage, so that the subsequent extraction and use can be conveniently realized when the target application is mounted again.
Optionally, referring to fig. 4, fig. 4 is a flowchart of another application management method provided in an embodiment of the present invention, and on the basis of fig. 2, before step 203, the application management method further includes the following steps:
step 401, according to the first target application information, calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language, so as to apply the first style to the first target application.
The hypertext Markup language may be html (hypertext Markup language). The first hypertext markup language is a hypertext markup language corresponding to the first target application. Each target application is provided with its own html. The style is an application style of a target application, and the first style is a style corresponding to a first target application. The style of each target application is injected by its corresponding html. And the html corresponding to each target application is unique.
Specifically, after the target application to be accessed by the user is determined to be the first target application, the first hypertext markup language of the first target application pair may be directly invoked, and then the corresponding first style is loaded to the first target application through the injection of the first hypertext markup language.
It should be noted that the first hypertext markup language and the first style are preset. Specifically, a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language are set for the first target application in advance, and the first hypertext markup language and the first style are stored.
It should be noted that, in the prior art, each target application has its own style, and when the number of target applications is multiple, or multiple target applications are developed in the same manner, or multiple target applications are developed for the same developer, it is inevitable to use the same identifier, such as the same letter or symbol, when naming the style of each target application. When each target application is used individually, there is no influence, but when a plurality of target applications are used in combination, there is pattern interference between the patterns of each target application when the plurality of target applications are used due to the same name or the like.
In the embodiment of the present invention, the first hypertext markup language and the first pattern of the first target application can be used separately, and specifically, the first pattern is loaded on the first target application through the first hypertext markup language. Because the hypertext markup language of each target application is unique, the pattern interference among a plurality of target applications can be avoided, and the global variable interference among the plurality of target applications can be avoided.
Preferably, referring to fig. 5, fig. 5 is a flowchart of another application management method provided in the embodiment of the present invention, and on the basis of fig. 4, before step 204, the application management method further includes the following steps:
step 501, a second hypertext markup language corresponding to a second target application and a second style corresponding to the second hypertext markup language are called, so that the second style is applied to the second target application.
And the second hypertext markup language is a hypertext markup language corresponding to the second target application. The second style is a style corresponding to the second target application.
Specifically, after the target application to be accessed by the user is determined to be the second target application, the second hypertext markup language of the second target application pair may be directly invoked, and then the second style corresponding to the second hypertext markup language is loaded to the second target application through the injection of the second hypertext markup language.
It should be noted that the second hypertext markup language and the second style are preset. Specifically, a corresponding second hypertext markup language and a second style corresponding to the second hypertext markup language are set for the second target application in advance, and the second hypertext markup language and the second style are stored.
In the embodiment of the present invention, the second hypertext markup language and the second style of the second target application can be used separately, and specifically, the second style is loaded to the second target application through the second hypertext markup language. Since the hypertext markup language of each target application is unique, style interference between the first target application and the second target application can be avoided. Furthermore, the pattern interference of a plurality of target applications can be avoided, and meanwhile, the global variable interference among the plurality of target applications can also be avoided.
Referring to fig. 6, fig. 6 is a schematic structural diagram of an application management apparatus according to an embodiment of the present invention, and as shown in fig. 6, the application management apparatus 600 includes:
the first obtaining module 601 is configured to obtain first mount request information for mounting a first target application, where the first mount request information carries first target application information corresponding to the first target application.
The first extracting module 602 is configured to extract a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information.
The first mounting module 603 is configured to determine the first global variable as the current global variable, so as to mount the first target application.
The second mounting module 604 is configured to, when the first target application is unloaded, change the first global variable into a second global variable to mount a second target application corresponding to the second global variable, where the second global variable is stored in a second preset sandbox corresponding to the second target application.
Optionally, on the basis of fig. 6, before the first obtaining module, the application management apparatus 600 further includes:
the system comprises a first preset module, a second preset module and a third preset module, wherein the first preset module is used for presetting a corresponding first preset sandbox for a first target application, and the first preset sandbox is used for storing a first global variable;
and the second preset module is used for setting a corresponding second preset sandbox for the second target application in advance, and the second preset sandbox is used for storing a second global variable.
Referring to fig. 7 and fig. 7 are schematic structural diagrams of another application management apparatus according to an embodiment of the present invention, on the basis of fig. 6, before the second mount module 603, the application management apparatus 600 further includes:
a determining module 605, configured to determine whether second mount request information for mounting a second target application is received, where the second mount information includes second target application information corresponding to the second target application;
the unloading module 606 is configured to, when receiving the second mount request information, return the first global variable to the first preset sandbox for storage, so as to unload the first target application;
a second extracting module 607, configured to extract a second global variable from a second preset sandbox according to the second target application information.
Referring to fig. 8, fig. 8 is a schematic structural diagram of another application management apparatus according to an embodiment of the present invention, and on the basis of fig. 6, before the first mount module 603, the application management apparatus 600 further includes:
the first calling module 608 is configured to call, according to the first target application information, a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language, so as to apply the first style to the first target application.
Referring to fig. 9, fig. 9 is a schematic structural diagram of another application management apparatus according to an embodiment of the present invention, and on the basis of fig. 8, before the second mount module, the application management apparatus 600 further includes:
the second invoking module 609 is configured to invoke a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language, so as to apply the second style to the second target application.
Optionally, on the basis of fig. 9, the application management apparatus 600 further includes:
the third preset module is used for setting a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language for the first target application in advance and storing the first hypertext markup language and the first style;
and the fourth preset module is used for setting a corresponding second hypertext markup language and a second style corresponding to the second hypertext markup language for the second target application in advance and storing the second hypertext markup language and the second style.
The application management device 600 provided in the embodiment of the present invention can implement each implementation manner in the above method embodiments and corresponding beneficial effects, and is not described here again to avoid repetition.
Referring to fig. 10, fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention, where the electronic device 700 includes: the memory 702, the processor 701 and a computer program stored on the memory 702 and operable on the processor 701, when the processor 701 executes the computer program, the steps in the application management method provided by the above embodiments are implemented, and the processor 701 executes the following steps:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining a first global variable as a current global variable so as to mount a first target application;
and when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
Optionally, the processor 701 further performs the following steps:
the method further comprises the following steps:
presetting a corresponding first preset sandbox for the first target application, wherein the first preset sandbox is used for storing a first global variable;
and setting a corresponding second preset sandbox for the second target application in advance, wherein the second preset sandbox is used for storing a second global variable.
Optionally, before the step that the processor 701 changes the first global variable into the second global variable when the first target application is uninstalled, so as to mount the second target application corresponding to the second global variable, the processor 701 further performs the following steps:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting information comprises second target application information corresponding to the second target application;
when second mounting request information is received, returning the first global variable to a first preset sandbox for storage so as to unload the first target application;
and extracting a second global variable from a second preset sandbox according to the second target application information.
Optionally, before the processor 701 determines the first global variable as the current global variable, and mounts the first target application, the processor 701 further performs the following steps:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
Optionally, before the processor 701 changes the first global variable into the second global variable to mount the second target application corresponding to the second global variable, the processor 701 further performs the following steps:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Optionally, the processor 701 further performs the following steps:
setting a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language for a first target application in advance, and storing the first hypertext markup language and the first style;
and setting a corresponding second hypertext markup language and a second style corresponding to the second hypertext markup language for the second target application in advance, and storing the second hypertext markup language and the second style.
The electronic device 700 may be an intelligent terminal, a mobile phone, a tablet computer, and the like of an application management system.
The electronic device 700 provided in the embodiment of the present invention can implement each implementation manner in the above method embodiments and corresponding beneficial effects, and is not described herein again to avoid repetition.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the application management method provided in the embodiment of the present invention, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.

Claims (10)

1. An application management method, characterized in that it comprises the following steps:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining the first global variable as a current global variable so as to mount the first target application;
when the first target application is unloaded, the first global variable is changed into a second global variable so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application.
2. The application management method of claim 1, wherein the method further comprises the steps of:
presetting the corresponding first preset sandbox for the first target application, wherein the first preset sandbox is used for storing the first global variable;
and presetting a corresponding second preset sandbox for the second target application, wherein the second preset sandbox is used for storing the second global variable.
3. The application management method according to claim 2, wherein before the step of changing the first global variable to a second global variable to mount a second target application corresponding to the second global variable when the first target application is uninstalled, the method further comprises the steps of:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting information comprises second target application information corresponding to the second target application;
when the second mounting request information is received, returning the first global variable to the first preset sandbox for storage so as to unload the first target application;
and extracting the second global variable from the second preset sandbox according to the second target application information.
4. The application management method of claim 1, wherein prior to said determining said first global variable as a current global variable for mounting a first target application, said method further comprises the steps of:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
5. The application management method according to claim 4, wherein before the changing the first global variable into a second global variable to mount a second target application corresponding to the second global variable, the method further comprises the steps of:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
6. The application management method of claim 5, wherein the method further comprises the steps of:
setting the corresponding first hypertext markup language and the first style corresponding to the first hypertext markup language for the first target application in advance, and storing the first hypertext markup language and the first style;
and setting the corresponding second hypertext markup language and the second style corresponding to the second hypertext markup language for the second target application in advance, and storing the second hypertext markup language and the second style.
7. An application management apparatus, characterized in that the application management apparatus comprises:
the system comprises a first obtaining module, a second obtaining module and a first loading module, wherein the first obtaining module is used for obtaining first loading request information for loading a first target application, and the first loading request information carries first target application information corresponding to the first target application;
the first extraction module is used for extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
the first mounting module is used for determining the first global variable as a current global variable so as to mount the first target application;
and the second mounting module is used for changing the first global variable into a second global variable when the first target application is unloaded so as to mount a second target application corresponding to the second global variable, and the second global variable is stored in a second preset sandbox corresponding to the second target application.
8. The application management apparatus according to claim 1, wherein the application management apparatus further comprises:
a first preset module, configured to set a corresponding first preset sandbox for the first target application in advance, where the first preset sandbox is used to store the first global variable;
and the second preset module is used for setting a corresponding second preset sandbox for the second target application in advance, and the second preset sandbox is used for storing the second global variable.
9. An electronic device, comprising: memory, processor and computer program stored on the memory and executable on the processor, the processor implementing the steps in the application management method according to any of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the application management method according to any one of claims 1 to 6.
CN201911414874.0A 2019-12-31 2019-12-31 Application management method and device, electronic equipment and storage medium Active CN113127010B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911414874.0A CN113127010B (en) 2019-12-31 2019-12-31 Application management method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911414874.0A CN113127010B (en) 2019-12-31 2019-12-31 Application management method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113127010A true CN113127010A (en) 2021-07-16
CN113127010B CN113127010B (en) 2023-11-17

Family

ID=76770476

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911414874.0A Active CN113127010B (en) 2019-12-31 2019-12-31 Application management method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113127010B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100011447A1 (en) * 2008-07-14 2010-01-14 Premkumar Jothimani Secure file processing
CN106874749A (en) * 2017-02-15 2017-06-20 青岛海信移动通信技术股份有限公司 A kind of method and apparatus for managing root authority

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100011447A1 (en) * 2008-07-14 2010-01-14 Premkumar Jothimani Secure file processing
CN106874749A (en) * 2017-02-15 2017-06-20 青岛海信移动通信技术股份有限公司 A kind of method and apparatus for managing root authority

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
刘俊琦;程虎;: "基于J2EE的应用支撑平台的设计与实现", 计算机工程与设计, no. 15 *

Also Published As

Publication number Publication date
CN113127010B (en) 2023-11-17

Similar Documents

Publication Publication Date Title
CN104572278B (en) The method, device and equipment of light application calling local side ability
CN103106102A (en) Running method of Web application program and mobile terminal
CN101571809A (en) Implementation method of plug-in registration and device thereof
CN104516885A (en) Implementation method and device of browse program double-kernel assembly
CN104756080A (en) Augmenting capabilities of a host device
CN110069919B (en) Information acquisition method and device
CN111639278A (en) Webpage loading method and device
CN107644075B (en) Method and device for collecting page information
CN111290949A (en) Process daemon method and equipment
CN105847319A (en) Mobile terminal network request method and system
CN108647102B (en) Service request processing method and device of heterogeneous system and electronic equipment
CN111679828B (en) Data processing method and device, electronic equipment and storage medium
CN112214250A (en) Application program assembly loading method and device
CN112650689A (en) Test method, test device, electronic equipment and storage medium
CN111414154A (en) Method and device for front-end development, electronic equipment and storage medium
CN113127010B (en) Application management method and device, electronic equipment and storage medium
CN112491943A (en) Data request method, device, storage medium and electronic equipment
CN114610446B (en) Method, device and system for automatically injecting probe
CN116304403A (en) Webpage access method and device, computer equipment and storage medium
CN115373998A (en) Application program optimization method, device, equipment and medium
CN107301089B (en) APP deployment and calling method and terminal
CN112346761B (en) Front-end resource online method, device, system and storage medium
CN111581578B (en) Interface request processing method and device
CN110471708B (en) Method and device for acquiring configuration items based on reusable components
CN104978199A (en) Plug-in application method and device used for multiple browsers

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant