CN114764354B - PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium - Google Patents
PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium Download PDFInfo
- Publication number
- CN114764354B CN114764354B CN202210410330.2A CN202210410330A CN114764354B CN 114764354 B CN114764354 B CN 114764354B CN 202210410330 A CN202210410330 A CN 202210410330A CN 114764354 B CN114764354 B CN 114764354B
- Authority
- CN
- China
- Prior art keywords
- target
- application
- sub
- resource
- dependent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 28
- 101150096185 PAAS gene Proteins 0.000 title claims abstract 6
- 230000001419 dependent effect Effects 0.000 claims abstract description 211
- 238000000034 method Methods 0.000 claims abstract description 45
- 238000012545 processing Methods 0.000 claims abstract description 13
- 230000008569 process Effects 0.000 claims abstract description 9
- 230000006870 function Effects 0.000 claims description 29
- 230000001960 triggered effect Effects 0.000 claims description 10
- 238000002347 injection Methods 0.000 claims description 4
- 239000007924 injection Substances 0.000 claims description 4
- 238000000926 separation method Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 8
- 238000010276 construction Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000012552 review Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 239000000243 solution Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/954—Navigation, e.g. using categorised browsing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44594—Unloading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/544—Buffers; Shared memory; Pipes
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a dependence management method, a device, electronic equipment and a medium based on PAAS. The method comprises the following steps: loading parent application information when a target child application is called; wherein the parent application information includes resource-dependent paths of the plurality of child applications; determining whether the target child application can share the path of the dependent resource in the parent application information based on the dependent configuration table of the target child application; the dependent configuration table stores paths of dependent resources which can be used by the target sub-application; if yes, determining a path of the sharable target dependent resource, and loading the target dependent resource based on the path of the target dependent resource; and after the target dependent resource is loaded, carrying out mounting processing based on the target dependent resource, and generating a sub-application instance to be displayed on the page. According to the method, the sub-application resource loading burden in the process of switching the sub-application is saved, and the resource display efficiency is improved, so that the user experience is improved.
Description
Technical Field
The present disclosure relates to computer network technologies, and in particular, to a dependency management method, apparatus, electronic device, and medium based on PAAS.
Background
Along with the continuous increase of business demands, codes of front-end engineering are gradually expanded, so that front-end applications are gradually developed into 'boulder applications', and great challenges are presented in the directions of application maintenance, application upgrading and the like.
To meet the challenges described above, the concept of micro front-end has been proposed. The micro front-end is a micro-service-like architecture, and the micro service concept is applied to the browser end, namely, web applications are converted from single application into a plurality of small front-end applications which are aggregated into one application, and each front-end application can be independently operated, independently developed and independently deployed.
For the mode, when the plurality of sub-applications load the resources, the resources are loaded in full quantity, meanwhile, due to the technical evolution of the modern front end, the resources to be loaded are often huge, so that the resource display efficiency is low when a user switches the sub-applications, and the user experience is not improved.
Disclosure of Invention
The application provides a dependence management method, a device, electronic equipment and a medium based on PAAS (advanced application server), which are used for reducing the burden of a front-end page, so that the efficiency of front-end resource display is improved, and further the user experience is improved.
In one aspect, the present application provides a dependency management method based on PAAS, the method comprising:
loading parent application information when a target child application is called; wherein the parent application information includes resource-dependent paths of a plurality of child applications;
determining whether the target child application can share a path of the dependent resource in the parent application information based on the dependent configuration table of the target child application; wherein the dependency configuration table stores paths of dependent resources usable by the target sub-application;
if yes, determining a path of a sharable target dependent resource, and loading the target dependent resource from a cache space based on the path of the target dependent resource, wherein the target dependent resource is a resource which is prestored to the cache space based on the path of the target dependent resource, and the cache space is used for caching the historically loaded dependent resource.
And after the target dependent resource is loaded, carrying out mounting processing based on the target dependent resource, and generating a sub-application instance to be displayed on a page.
In another possible implementation manner, if there are a plurality of target dependent resources, the loading the target dependent resources from the cache space based on the path of the target dependent resources includes:
adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in the asynchronous queue according to a preset rule;
and loading the target dependent resource based on a minimum system loading tool after the target dependent resource is pulled.
In another possible implementation manner, before the calling the target sub-application, the method further includes:
acquiring sub-application information triggered by a user on a navigation page, wherein the sub-application information is a webpage address input by the user or a sub-application identifier selected by the user;
and determining the target sub-application to be called based on the sub-application information.
In another possible implementation, the method further includes:
and if the target dependent resource does not exist in the cache space, loading the target dependent resource according to the path of the target dependent resource.
In another possible implementation manner, the method performs a mounting process based on the target dependent resource, and generates a sub-application instance to be displayed before the page, and the method further includes:
acquiring path configuration information of the target sub-application, wherein the path configuration information comprises a path of a resource to be loaded of the target sub-application;
determining paths of independent resources except the target dependent resources according to the paths of the resources to be loaded;
loading the independent resources of the target sub-application based on the paths of the independent resources;
in another possible implementation manner, the performing the mounting process based on the target dependent resource, and generating a sub-application instance to be displayed on a page, includes:
and carrying out mounting processing based on the target dependent resource and the independent resource, and generating a sub-application instance to be displayed on a page.
In another possible implementation manner, if the target child application cannot share the path of the dependent resource in the parent application information, the method further includes:
carrying out full load on the resources to be loaded based on the path configuration information;
and updating the parent application information based on the resource-dependent path in the path configuration information.
In another possible implementation, when it is determined that the target child application does not share the dependent resource of the parent application, the method further includes:
acquiring a configuration file of the target sub-application, wherein the configuration file comprises a plurality of compiling hook functions;
determining an objective hook function corresponding to each objective dependent resource in a plurality of compiling hook functions based on the objective dependent resources of the sharable parent application;
separating the target dependent resources based on the target hook function;
and acquiring script codes corresponding to the target dependent resources, and injecting the script codes into source codes of the target sub-application to realize independent operation of the target sub-application.
In another possible implementation manner, after the target dependent resource is loaded, the mounting process is performed based on the target dependent resource, and the sub application instance is generated and displayed after the page, and the method further includes:
judging whether the target sub-application is switched or closed currently;
if yes, unloading the current target sub-application based on an unloading event, wherein the unloading event is specifically an umount command and is used for forcedly unloading the sub-application information.
In another possible implementation manner, the determining whether the target sub-application is currently switched or closed includes:
acquiring current sub-application information triggered by a user on a navigation page;
and if the current sub-application information is inconsistent with the acquired sub-application information, determining that the target sub-application is switched or closed.
In another aspect, the present application provides an industrial PAAS-based dependency management apparatus, comprising:
the first loading module is used for loading father application information when the target child application is called; wherein the parent application information includes resource-dependent paths of a plurality of child applications;
a first determining module, configured to determine, based on a dependency configuration table of the target child application, whether the target child application can share a path of a dependent resource in the parent application information; wherein the dependency configuration table stores paths of dependent resources usable by the target sub-application;
a second loading module, configured to determine a path of a sharable target dependent resource when the target child application can share the path of the dependent resource in the parent application information, and load the target dependent resource from a cache space based on the path of the target dependent resource, where the target dependent resource is a resource that is prestored in the cache space based on the target dependent resource path, and the cache space is used for caching the historically loaded dependent resource;
and the display module is used for carrying out mounting processing based on the target dependent resources after the target dependent resources are loaded, and generating a sub-application instance to be displayed on a page.
In another possible implementation manner, when there are a plurality of target dependent resources, the second loading module is specifically configured to:
adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in the asynchronous queue according to a preset rule;
and loading the target dependent resource based on a minimum system loading tool after the target dependent resource is pulled.
In another possible implementation, the apparatus further includes:
the first acquisition module is used for acquiring sub-application information triggered by a user on a navigation page, wherein the sub-application information is a webpage address input by the user or a sub-application identifier selected by the user;
and the second determining module is used for determining the target sub-application to be called based on the sub-application information.
In another possible implementation, the apparatus further includes:
and the third loading module is used for loading the target dependent resource according to the path of the target dependent resource when the target dependent resource does not exist in the cache space.
In another possible implementation, the apparatus further includes:
the second acquisition module is used for acquiring path configuration information of the target sub-application, wherein the path configuration information comprises a path of a resource to be loaded of the target sub-application;
a third determining module, configured to determine, according to the path of the resource to be loaded, a path of an independent resource other than the target dependent resource;
a fourth loading module, configured to load the independent resource of the target sub-application based on the path of the independent resource;
in another possible implementation manner, the display module is specifically configured to:
and carrying out mounting processing based on the target dependent resource and the independent resource, and generating a sub-application instance to be displayed on a page.
In another possible implementation, the apparatus further includes:
the fifth loading module is used for carrying out full-load on the resources to be loaded based on the path configuration information;
and the updating module is used for updating the father application information based on the resource-dependent path in the path configuration information.
In another possible implementation, the apparatus further includes:
the third acquisition module is used for acquiring a configuration file of the target sub-application, wherein the configuration file comprises a plurality of compiling hook functions;
a fourth determining module, configured to determine, based on target dependent resources of a sharable parent application, a target hook function corresponding to each target dependent resource among a plurality of compiled hook functions;
a separation module for separating the target dependent resources based on the target hook function;
and the injection module is used for acquiring the script code corresponding to the target dependent resource and injecting the script code into the source code of the target sub-application so as to realize independent operation of the target sub-application.
In another possible implementation, the apparatus further includes:
the judging module is used for judging whether the target sub-application is switched or closed currently;
and the unloading module is used for unloading the current target sub-application based on an unloading event, specifically an umount command, when the current target sub-application is switched or closed, and is used for forcibly unloading the sub-application information.
In another possible implementation manner, the unloading module is specifically configured to:
acquiring current sub-application information triggered by a user on a navigation page;
and if the current sub-application information is inconsistent with the acquired sub-application information, determining that the target sub-application is switched or closed.
In a third aspect, the present invention provides an electronic device comprising:
at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the memory-stored computer-executable instructions causes the at least one processor to perform the PAAS-based dependency management method as set forth in any one of the first aspects above.
In a fourth aspect, the present invention provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, implement a PAAS-based dependency management method as set forth in any one of the first aspects above.
The application provides a dependence management method, a device, an electronic device and a medium based on PAAS, wherein after a user determines a target sub-application on a page, the electronic device can load the resource to be loaded of the target sub-application through the parent application, and the specific loading flow is as follows: first, based on the dependency configuration table of the target child application, it is determined whether a shareable dependency exists between the target child application and the parent application. If there is a shareable dependency between the target sub-application and the parent application, the electronic device determines whether the target dependent resource is cached in the cache space based on the dependency configuration table, and if there is the target dependent resource cached in the cache space, directly pulls the target dependent resource from the cache space, thereby saving time for loading the target dependent resource, reducing loading time of the target sub-application to-be-loaded resource, and further being beneficial to improving user experience.
For the target dependent resources and independent resources except the target dependent resources which are not in the cache space, the electronic equipment loads the resources based on the path configuration information of the target sub-application so as to ensure the resource integrity of the target sub-application. And after the resource to be loaded is loaded, generating an instance based on the resource to be loaded and displaying the instance on a page for the user to review.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a system schematic diagram of an industrial PAAS-based dependency management system according to an embodiment of the present application;
FIG. 2 is a user page interaction diagram provided in an embodiment of the present application;
FIG. 3a is a schematic diagram of a PAAS-based dependency management method according to an embodiment of the present application;
FIG. 3b is a flowchart of a PAAS-based dependency management method according to an embodiment of the present application;
FIG. 4 is a flowchart of sub-application construction provided in an embodiment of the present application;
FIG. 5 is a schematic structural diagram of a dependency management apparatus based on industrial PAAS according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
FIG. 1 is a system diagram of dependency management based on industrial PAAS according to an embodiment of the present application. As shown in fig. 1, the system provided in the embodiment of the present application includes a terminal and a server, where the terminal may be a device that may interact with a user, such as a computer, a mobile phone, a tablet, or the like. For example, the terminal may be a computer as shown in fig. 1. The computer communicates with the server via a network.
Fig. 2 is a user page interaction diagram provided in an embodiment of the present application. As shown in fig. 2, the child application registers to the parent application in advance, when the user opens the navigation page on the computer and inputs any address or selects any identifier on the navigation page, the electronic device determines the target child application required to be started by the user based on the address or the identifier, controls the computer page to jump to the page of the target child application, and controls the server to load the resource to be loaded of the target child application. The electronic equipment based on the resources to be loaded can generate an instance and display the instance on a computer page for the user to review. Because a plurality of sub-applications which can be started by the user exist in the navigation page, the user can randomly switch the target sub-applications based on the requirement. When a user switches the target sub-application or closes the current target sub-application, after unloading the resources loaded by the previous target sub-application, loading the resources of the switched target sub-application and finally displaying the resources on a computer page, or directly closing the page.
For the above process, when the next target sub-application is switched, the resources of the next target sub-application are loaded in full, and due to the technical evolution of the modern front end, the loaded resources are often huge, so that the loading efficiency is low. Because the resources among the sub-applications have quite large commonality, namely sharing dependence exists among the sub-applications, the application provides a dependence management method based on PAAS (application specific application) so as to manage the dependence resources when the sub-applications load the resources, thereby achieving the effects of greatly accelerating the loading speed of pages, reducing the occupation of network resources and relieving the execution burden of js engines, and being beneficial to improving the use experience of users.
Fig. 3a is a schematic diagram of a PAAS-based dependency management method according to an embodiment of the present application, and fig. 3b is a flowchart of a PAAS-based dependency management method according to an embodiment of the present application. Some embodiments of the present application are described in detail below in conjunction with fig. 3a and 3 b. In the case where the embodiments do not conflict, the following embodiments and features in the embodiments may be combined with each other.
As shown in FIG. 3a, the parent application is used to load the underlying common dependencies at initialization for invocation at loading of the various child applications. The plurality of sub-applications register the service in advance and write the sub-application information into the parent application. Specifically, the sub-applications include a route manager and an application manager. When the child application is loaded through the parent application, a resource path of the child application is obtained first, and whether dependency sharing exists between the child application and the parent application or not is judged based on the resource path of the child application. If there is a dependency sharing between the child application and the parent application, the child application resource is loaded according to the dependency loader. If the child application and the parent application do not rely on sharing, the resource to be loaded is loaded in full quantity directly according to the resource path of the child application. And mounting the loaded sub-application resources, generating sub-application instances based on the sub-application resources, and displaying the sub-application instances. Wherein the process of loading sub-application resources based on a dependency loader is described in detail in the following embodiments.
As shown in fig. 3b, the method in the present embodiment may include step S301, step S302, step S303, and step S304, wherein,
in step S301, when the target child application is invoked, parent application information is loaded.
The parent application information comprises resource-dependent paths of a plurality of child applications, and the child application information comprises information such as child application webpage addresses, child application identifications, path configuration of resources to be loaded and the like. The electronic device needs to determine the target sub-application by the user before invoking the target sub-application.
Optionally, the manner in which the user determines the target sub-application may include: and acquiring sub-application information triggered by the user on the navigation page, and determining a target sub-application to be called based on the sub-application information.
Specifically, the sub-application information is a webpage address input by a user or a sub-application identifier selected by the user, wherein the sub-application identifier can be a text identifier or a graphic identifier. Assuming that the web page address of a sub-application is "xxx.com/abc" and labeled as "weather", when the user inputs the address "xxx.com/abc" on the navigation page or selects the "weather" label, the sub-application is determined to be the target sub-application.
Step S302, based on the dependency configuration table of the target sub-application, determining whether the target sub-application can share the path of the dependent resource in the parent application information.
The dependent configuration table is provided by the target sub-application, stores paths of dependent resources which can be used by the target sub-application, and is manually configured and written into the sub-application in advance. The method for determining whether the target child application can share the path of the dependent resource in the parent application information can be as follows: the path of the usable dependent resource of the target sub-application is searched in the parent application information, and the path which indicates that the target sub-application can share the dependent resource in the parent application information can be searched, and the path which indicates that the target sub-application cannot share the dependent resource in the parent application information can be not searched.
Step S303, if yes, determining a path of the sharable target dependent resource, and loading the target dependent resource from the cache space based on the path of the target dependent resource.
The method comprises the step of determining a path of a sharable target dependent resource, namely determining a path of the target dependent resource of a target sub-application from parent application information. When the child application resource is loaded based on the parent application, the electronic device stores the dependent resource which is loaded in history into the cache space. When the target dependent resource which is selected or switched by the user and can share the dependence with the father application is overlapped with the dependent resource which is loaded in history, the corresponding dependent resource can be directly pulled from the cache space.
Specifically, the method for the electronic device to determine whether the target dependent resource is a resource that is pre-stored into the cache space based on the target resource dependent path may be: and searching the paths of the target dependent resources in the paths of the resources contained in the cache space.
Optionally, when there are multiple target dependent resources, loading the target dependent resources from the cache space based on the paths of the target dependent resources may include: adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in sequence based on an import sequence (import-maps); after the target dependent resource pulling is completed, the target dependent resource is loaded based on a minimum system loading tool (systemJs).
Optionally, when the target dependent resource cannot be found in the cache space, loading the target dependent resource according to the path of the target dependent resource. And for the target dependent resources which cannot be found in the cache space, the electronic equipment loads the target dependent resources according to the paths of the corresponding target dependent resources.
And step S304, after the target dependent resource loading is completed, carrying out mounting processing based on the target dependent resource, and generating a sub-application instance to be displayed on the page.
Optionally, before the mounting process is performed based on the target dependent resource and the sub-application instance is generated and displayed on the page, a path of the resource to be loaded of the target sub-application is obtained, a path of an independent resource except the target dependent resource is determined according to the path of the resource to be loaded, and the independent resource of the target sub-application is loaded based on the path of the independent resource.
After the independent resources exist in the target sub-application and the independent resources are loaded, carrying out mounting processing based on the loaded independent resources and the dependent resources, generating a sub-application instance and displaying the sub-application instance on the page.
Optionally, when the user switches or closes the target sub-application, the electronic device destroys the route and the instance through an unloading event (umount event), and finishes the unloading of the sub-application, so that the target sub-application is switched or closed.
Specifically, the manner in which the electronic device determines whether the target sub-application is switched or closed may be: and acquiring current sub-application information, judging whether the current sub-application information is consistent with the sub-application information of the target sub-application, and if not, indicating that the target sub-application is switched or closed by a user.
Based on the technical solution provided in the foregoing embodiment, optionally, when the target child application cannot share the path of the dependent resource in the parent application information, the method further includes: carrying out full-load on the resources to be loaded based on the path configuration information; and updating the parent application information based on the resource-dependent path in the path configuration information.
Specifically, when no dependency relationship exists between the target child application and the parent application, the resource to be loaded is directly loaded through the path configuration information of the target child application. Meanwhile, the registration of the target sub-application is completed, the target sub-application information is written into the parent application, and the update of the parent application is completed.
Based on the technical solution provided in the foregoing embodiment, optionally, when determining that the target child application does not share the dependent resource of the parent application, the method further includes: acquiring a configuration file of a target sub-application, wherein the configuration file comprises a plurality of compiling hook functions; determining an objective hook function corresponding to each objective dependent resource in a plurality of compiling hook functions based on the objective dependent resources of the sharable parent application; separating target dependent resources based on a target hook function; and acquiring script codes corresponding to the target dependent resources, and injecting the script codes into source codes of the target sub-application to realize independent operation of the target sub-application.
Specifically, as shown in the construction flow of the child application in fig. 4, before compiling the child application, it is first determined whether the child application has a configuration file, if not, the child application is directly compiled, and at this time, the child application needs to be loaded by the parent application. If so, searching a hook function, entering the hook function, analyzing the source code according to the configuration file, generating a dependency injection code to rewrite the source code, compiling at the moment, and outputting a compiling result according to the configuration file so that the child application can load independent resources without attaching to the parent application.
In addition, before the construction parent application enters the compiling link, the configuration file should be read first, and the configuration file configures plug-ins and various configuration parameters required by each construction link. Meanwhile, if the parent application plugin is included, the child configuration table is read again. When the parent application needs to load the basic module, the parent application enters a compiling hook function to find an objective hook function, analyzes source codes after entering the objective hook function, separates dependence according to a configuration file, rewrites the source codes and then injects the source codes into the self-executing script codes.
According to the method provided by the embodiment, when a user opens any target child application, the electronic device can firstly load the parent application, so that the parent application is in a usable state. If shareable dependence exists between the target sub-application and the parent application and corresponding target dependent resources can be found in the cache space, the target dependent resources are directly loaded from the cache space, so that time for reloading the target dependent resources based on a target dependent resource path of the target sub-application is saved, the opening or switching efficiency of the target sub-application is improved, and user experience is improved. Meanwhile, when the independent resources which are not shared with the parent application exist in the resources to be loaded of the target child application, after the independent resources and the target dependent resources which need to be reloaded are loaded based on the path configuration information, the resources to be loaded are mounted, and the generated examples are displayed on a page for the user to review.
The above embodiment describes a dependency management method based on PAAS from the aspect of a method flow, and the following embodiment describes a dependency management apparatus based on industrial PAAS from the aspect of a virtual module or a virtual unit, specifically the following embodiment.
The embodiment of the application provides a dependency management apparatus based on industrial PAAS, as shown in fig. 5, which includes a first loading module 51, a first determining module 52, a second loading module 53 and a display module 54, wherein,
a first loading module 51, configured to load parent application information when a target child application is invoked; wherein the parent application information includes resource-dependent paths of the plurality of child applications;
a first determining module 52, configured to determine, based on the dependency configuration table of the target child application, whether the target child application can share the path of the dependent resource in the parent application information; the dependent configuration table stores paths of dependent resources which can be used by the target sub-application;
a second loading module 53, configured to determine a path of a sharable target dependent resource when the target child application may share the path of the dependent resource in the parent application information, and load the target dependent resource from a cache space based on the path of the target dependent resource, where the target dependent resource is a resource that is stored in advance into the cache space based on the path of the target dependent resource, and the cache space is used to cache the dependent resource loaded in history;
and the display module 54 is used for carrying out mounting processing based on the target dependent resources after the target dependent resources are loaded, and generating a sub-application instance to be displayed on the page.
Another possible implementation manner of the embodiment of the present application, when there are multiple target dependent resources, the second loading module 53 is specifically configured to:
adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in the asynchronous queue according to a preset rule;
after the target dependent resource pulling is completed, the target dependent resource is loaded based on a minimum system loading tool (systemJs).
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
the first acquisition module is used for acquiring sub-application information triggered by a user on a navigation page, wherein the sub-application information is a webpage address input by the user or a sub-application identifier selected by the user;
and the second determining module is used for determining the target sub-application to be called based on the sub-application information.
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
and the third loading module is used for loading the target dependent resource according to the path of the target dependent resource when the target dependent resource does not exist in the cache space.
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
the second acquisition module is used for acquiring path configuration information of the target sub-application, wherein the path configuration information comprises paths of resources to be loaded of the target sub-application;
the third determining module is used for determining paths of independent resources except the target dependent resources according to paths of the resources to be loaded;
and the fourth loading module is used for loading the independent resources of the target sub-application based on the paths of the independent resources.
In another possible implementation manner of the embodiment of the present application, the display module 54 is specifically configured to:
and carrying out mounting processing based on the target dependent resources and the independent resources, and generating a sub-application instance to be displayed on the page.
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
the fifth loading module is used for carrying out full-load loading on the resources to be loaded based on the path configuration information;
and the updating module is used for updating the father application information based on the path depending on the resource in the path configuration information.
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
the third acquisition module is used for acquiring a configuration file of the target sub-application, wherein the configuration file comprises a plurality of compiling hook functions;
a fourth determining module, configured to determine, based on target dependent resources of the sharable parent application, a target hook function corresponding to each target dependent resource among a plurality of compiled hook functions;
a separation module for separating target dependent resources based on a target hook function;
the injection module is used for acquiring script codes corresponding to the target dependent resources and injecting the script codes into the source codes of the target sub-applications so as to realize independent operation of the target sub-applications.
Another possible implementation manner of the embodiment of the present application, the apparatus further includes:
and the judging module is used for judging whether the current target sub-application is switched or closed.
And the unloading module is used for unloading the current target sub-application based on an unloading event, specifically an umount command, when the current target sub-application is switched or closed, and is used for forcedly unloading the sub-application information.
In another possible implementation manner of the embodiment of the present application, the unloading module is specifically configured to:
acquiring current sub-application information triggered by a user on a navigation page;
and if the current sub-application information is inconsistent with the acquired sub-application information, determining that the target sub-application is switched or closed.
In this embodiment of the present application, the first loading module 51, the second loading module 53, the third loading module, the fourth loading module and the fifth loading module may be the same loading module, may be different loading modules, or may be partially the same loading module. The first determining module 52, the second determining module, the third determining module, and the fourth determining module may be the same determining module, may be different determining modules, or may be partially the same determining module. The first acquisition module, the second acquisition module and the third acquisition module may be the same acquisition module, may be different acquisition modules, or may be partially identical acquisition modules. The embodiments of the present application are not limited.
The dependency management apparatus based on industrial PAAS provided in the embodiments of the present application is applicable to the above method embodiments, and is not described herein again.
In an embodiment of the present application, as shown in fig. 6, an electronic device shown in fig. 6 includes: a processor 61 and a memory 62. Wherein the processor 61 is coupled to the memory 62, such as via a bus 63. Optionally, the electronic device may also include a transceiver 64. It should be noted that, in practical applications, the transceiver 64 is not limited to one, and the structure of the electronic device is not limited to the embodiment of the present application.
The processor 61 may be a central processor 61 (Central Processing Unit, CPU), general purpose processor 61, data signal processor 61 (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor 61 may also be a combination that implements computing functionality, such as a combination comprising one or more microprocessors 61, a combination of a DSP and a microprocessor 61, or the like.
Bus 63 may include a path to transfer information between the aforementioned components. The bus 63 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus 63, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus 63, among others. The bus 63 may be divided into an address bus 63, a data bus 63, a control bus 63, and the like. For ease of illustration, only one thick line is shown in fig. 6, but not only one bus 63 or one type of bus 63.
The Memory 62 may be, but is not limited to, a Read Only Memory 62 (ROM) or other type of static storage device that can store static information and instructions, a random access Memory 62 (Random Access Memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable Read Only Memory 62 (Electrically Erasable Programmable Read Only Memory, EEPROM), a compact disc Read Only Memory (Compact Disc Read Only Memory, CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The memory 62 is used for storing application program codes for executing the present application and is controlled to be executed by the processor 61. The processor 61 is arranged to execute application code stored in the memory 62 for implementing what is shown in the previous method embodiments.
Among them, electronic devices include, but are not limited to: mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal Digital Assistants (PDAs), tablet computers (PADs), portable Multimedia Players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. But may also be a server or the like. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
The present application provides a computer readable storage medium having a computer program stored thereon, which when run on a computer, causes the computer to perform the corresponding method embodiments described above.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (14)
1. A PAAS-based dependency management method, comprising:
loading parent application information when a target child application is called; wherein the parent application information includes resource-dependent paths of a plurality of child applications;
determining whether the target child application can share a path of the dependent resource in the parent application information based on the dependent configuration table of the target child application; wherein the dependency configuration table stores paths of dependent resources usable by the target sub-application;
if yes, determining a path of a sharable target dependent resource, and loading the target dependent resource from a cache space based on the path of the target dependent resource, wherein the target dependent resource is a resource which is prestored to the cache space based on the path of the target dependent resource, and the cache space is used for caching the historically loaded dependent resource;
after the target dependent resource is loaded, carrying out mounting processing based on the target dependent resource, and generating a sub-application instance to be displayed on a page;
upon determining that the target child application does not share the dependent resources of the parent application, the method further comprises:
acquiring a configuration file of the target sub-application, wherein the configuration file comprises a plurality of compiling hook functions;
determining an objective hook function corresponding to each objective dependent resource in a plurality of compiling hook functions based on the objective dependent resources of the sharable parent application;
separating the target dependent resources based on the target hook function;
and acquiring script codes corresponding to the target dependent resources, and injecting the script codes into source codes of the target sub-application to realize independent operation of the target sub-application.
2. The method of claim 1, wherein if there are a plurality of the target-dependent resources, the loading the target-dependent resources from the cache space based on the target-dependent resource path comprises:
adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in the asynchronous queue according to a preset rule;
and loading the target dependent resource based on a minimum system loading tool after the target dependent resource is pulled.
3. The method of claim 1, wherein prior to the invoking the target sub-application, the method further comprises:
acquiring sub-application information triggered by a user on a navigation page, wherein the sub-application information is a webpage address input by the user or a sub-application identifier selected by the user;
and determining the target sub-application to be called based on the sub-application information.
4. The method according to claim 1, wherein the method further comprises:
and if the target dependent resource does not exist in the cache space, loading the target dependent resource according to the path of the target dependent resource.
5. The method of claim 1, wherein the mounting is based on the target dependent resource and the generating a child application instance is displayed before the page, the method further comprising:
acquiring path configuration information of the target sub-application, wherein the path configuration information comprises a path of a resource to be loaded of the target sub-application;
determining paths of independent resources except the target dependent resources according to the paths of the resources to be loaded;
and loading the independent resources of the target sub-application based on the paths of the independent resources.
6. The method of claim 5, wherein the performing the mounting process based on the target dependent resource and generating the sub-application instance to be displayed on the page comprise:
and carrying out mounting processing based on the target dependent resource and the independent resource, and generating a sub-application instance to be displayed on a page.
7. The method of claim 5, wherein if the target child application cannot share a resource-dependent path in the parent application information, the method further comprises:
carrying out full load on the resources to be loaded based on the path configuration information;
and updating the parent application information based on the resource-dependent path in the path configuration information.
8. The method of claim 3, wherein after the target dependent resource loading is completed, performing a mount process based on the target dependent resource, and generating a sub-application instance to be displayed after a page, the method further comprising:
judging whether the target sub-application is switched or closed currently;
if yes, unloading the current target sub-application based on an unloading event, wherein the unloading event is specifically an umount command and is used for forcedly unloading the sub-application information.
9. The method of claim 8, wherein said determining whether the current target sub-application is switched or closed comprises:
acquiring current sub-application information triggered by a user on a navigation page;
and if the current sub-application information is inconsistent with the acquired sub-application information, determining that the target sub-application is switched or closed.
10. An industrial PAAS-based dependency management apparatus, comprising:
the first loading module is used for loading father application information when the target child application is called; wherein the parent application information includes resource-dependent paths of a plurality of child applications;
a first determining module, configured to determine, based on a dependency configuration table of the target child application, whether the target child application can share a path of a dependent resource in the parent application information; wherein the dependency configuration table stores paths of dependent resources usable by the target sub-application;
a second loading module, configured to determine a path of a sharable target dependent resource when the target child application can share the path of the dependent resource in the parent application information, and load the target dependent resource from a cache space based on the path of the target dependent resource, where the target dependent resource is a resource that is prestored in the cache space based on the target dependent resource path, and the cache space is used for caching the historically loaded dependent resource;
the display module is used for carrying out mounting processing based on the target dependent resources after the target dependent resources are loaded, and generating a sub-application instance to be displayed on a page;
a third obtaining module, configured to obtain a configuration file of the target child application when it is determined that the target child application does not share the dependent resource of the parent application, where the configuration file includes a plurality of compiling hook functions;
a fourth determining module, configured to determine, based on target dependent resources of the sharable parent application, a target hook function corresponding to each target dependent resource among the plurality of compiled hook functions;
a separation module for separating the target dependent resources based on the target hook function;
and the injection module is used for acquiring the script code corresponding to the target dependent resource and injecting the script code into the source code of the target sub-application so as to realize independent operation of the target sub-application.
11. The apparatus of claim 10, wherein the second loading module is specifically configured to:
adding a plurality of target dependent resources to an asynchronous queue, and pulling the target dependent resources in the asynchronous queue according to a preset rule;
and loading the target dependent resource based on a minimum system loading tool after the target dependent resource is pulled.
12. The apparatus of claim 10, wherein the apparatus further comprises:
the first acquisition module is used for acquiring sub-application information triggered by a user on a navigation page, wherein the sub-application information is a webpage address input by the user or a sub-application identifier selected by the user;
and the second determining module is used for determining the target sub-application to be called based on the sub-application information.
13. An electronic device, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing computer-executable instructions stored in the memory cause the at least one processor to perform the PAAS-based dependency management method as recited in any one of claims 1-9.
14. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing a PAAS based dependency management method as claimed in any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210410330.2A CN114764354B (en) | 2022-04-19 | 2022-04-19 | PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210410330.2A CN114764354B (en) | 2022-04-19 | 2022-04-19 | PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114764354A CN114764354A (en) | 2022-07-19 |
| CN114764354B true CN114764354B (en) | 2024-01-05 |
Family
ID=82364880
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210410330.2A Active CN114764354B (en) | 2022-04-19 | 2022-04-19 | PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114764354B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117648179A (en) * | 2023-11-23 | 2024-03-05 | 北京菱云科技有限公司 | Resource allocation method and device, electronic equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354049A (en) * | 2015-09-29 | 2016-02-24 | 北京畅游天下网络技术有限公司 | Resource loading method, apparatus and system for three-dimensional animation engine |
| CN107105336A (en) * | 2017-04-19 | 2017-08-29 | 腾讯科技（深圳）有限公司 | Data processing method and data processing equipment |
| US9928058B1 (en) * | 2014-10-28 | 2018-03-27 | Amazon Technologies, Inc. | Optimized class loading |
| CN108108205A (en) * | 2016-11-25 | 2018-06-01 | 腾讯科技（深圳）有限公司 | Application page surface treatment method and apparatus |
| CN110298002A (en) * | 2019-05-31 | 2019-10-01 | 福建新大陆软件工程有限公司 | Client WEB method for managing resource and equipment |
| CN110865888A (en) * | 2019-11-28 | 2020-03-06 | 米哈游科技（上海）有限公司 | Resource loading method and device, server and storage medium |
| CN111198730A (en) * | 2018-10-30 | 2020-05-26 | 广州腾讯科技有限公司 | Method, device, terminal and computer storage medium for starting sub-application program |
| CN112306587A (en) * | 2019-07-15 | 2021-02-02 | 腾讯科技（深圳）有限公司 | Page display processing method and device and terminal equipment |
| CN113065085A (en) * | 2021-03-22 | 2021-07-02 | 北京沃东天骏信息技术有限公司 | Data loading method and device, target server, target terminal and storage medium |
| CN113064676A (en) * | 2020-12-29 | 2021-07-02 | 上海金融期货信息技术有限公司 | Method for remote component sharing mechanism during front-end operation based on JS entrance |
| CN113204726A (en) * | 2021-07-07 | 2021-08-03 | 苏州浪潮智能科技有限公司 | BS architecture page response time optimization method, device, equipment and medium |
| CN113254237A (en) * | 2021-06-11 | 2021-08-13 | 海尔数字科技(青岛)有限公司 | Front-end application calling method, device, storage medium and program product |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107102880B (en) * | 2017-05-11 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Message treatment method, device, storage medium and computer equipment |
| CN109814939B (en) * | 2017-11-20 | 2021-10-15 | 华为技术有限公司 | Dynamic loading method, and target file manufacturing method and device |
-
2022
- 2022-04-19 CN CN202210410330.2A patent/CN114764354B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9928058B1 (en) * | 2014-10-28 | 2018-03-27 | Amazon Technologies, Inc. | Optimized class loading |
| CN105354049A (en) * | 2015-09-29 | 2016-02-24 | 北京畅游天下网络技术有限公司 | Resource loading method, apparatus and system for three-dimensional animation engine |
| CN108108205A (en) * | 2016-11-25 | 2018-06-01 | 腾讯科技（深圳）有限公司 | Application page surface treatment method and apparatus |
| CN107105336A (en) * | 2017-04-19 | 2017-08-29 | 腾讯科技（深圳）有限公司 | Data processing method and data processing equipment |
| CN111198730A (en) * | 2018-10-30 | 2020-05-26 | 广州腾讯科技有限公司 | Method, device, terminal and computer storage medium for starting sub-application program |
| CN110298002A (en) * | 2019-05-31 | 2019-10-01 | 福建新大陆软件工程有限公司 | Client WEB method for managing resource and equipment |
| CN112306587A (en) * | 2019-07-15 | 2021-02-02 | 腾讯科技（深圳）有限公司 | Page display processing method and device and terminal equipment |
| CN110865888A (en) * | 2019-11-28 | 2020-03-06 | 米哈游科技（上海）有限公司 | Resource loading method and device, server and storage medium |
| CN113064676A (en) * | 2020-12-29 | 2021-07-02 | 上海金融期货信息技术有限公司 | Method for remote component sharing mechanism during front-end operation based on JS entrance |
| CN113065085A (en) * | 2021-03-22 | 2021-07-02 | 北京沃东天骏信息技术有限公司 | Data loading method and device, target server, target terminal and storage medium |
| CN113254237A (en) * | 2021-06-11 | 2021-08-13 | 海尔数字科技(青岛)有限公司 | Front-end application calling method, device, storage medium and program product |
| CN113204726A (en) * | 2021-07-07 | 2021-08-03 | 苏州浪潮智能科技有限公司 | BS architecture page response time optimization method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114764354A (en) | 2022-07-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8739147B2 (en) | Class isolation to minimize memory usage in a device | |
| US7877091B2 (en) | Method and system for executing a container managed application on a processing device | |
| US20170357735A1 (en) | Information presentation method, device, and system | |
| CN111666497B (en) | Application program loading method and device, electronic equipment and readable storage medium | |
| US11474810B2 (en) | Run-time application modification | |
| CN111372115B (en) | Application program access method and device and communication system | |
| US8984542B2 (en) | Method and system for binding objects in dynamic programming languages using caching techniques | |
| CN114764354B (en) | PAAS-based dependency management method, PAAS-based dependency management device, electronic equipment and medium | |
| US20040123308A1 (en) | Hybird of implicit and explicit linkage of windows dynamic link labraries | |
| WO2013176967A1 (en) | Virtualizing integrated calls to provide access to resources in a virtual namespace | |
| US10303523B2 (en) | Method and apparatus to migrate stacks for thread execution | |
| CN111459481A (en) | Page sideslip method and device, electronic equipment and storage medium | |
| CN111722888B (en) | Operation execution method, device, equipment and readable storage medium | |
| CN114637969A (en) | Target object authentication method and device | |
| CN111931111A (en) | Webpage development method, webpage display method, device and equipment | |
| CN111142972A (en) | Method, apparatus, system, and medium for extending functions of application program | |
| CN116400945B (en) | Dynamic link library upgrading method, electronic equipment and storage medium | |
| CN116700694B (en) | Applet engine | |
| CN113704187B (en) | Method, apparatus, server and computer readable medium for generating file | |
| CN116737251A (en) | Starting method, starting device, terminal equipment and medium | |
| CN113835596A (en) | Icon processing method, device and equipment | |
| CN115309471A (en) | Application program starting method, device, equipment and medium | |
| Silva et al. | Migration of a microservice from Payara Micro to Quarkus and performance analysis | |
| CN117369910A (en) | Resource processing method and device based on micro-application architecture and electronic equipment | |
| CN116089107A (en) | Module initialization method, device, equipment and cache medium |
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 | ||
| CP03 | Change of name, title or address |
Address after: 266500 No. 1, Minshan Road, Qingdao area, China (Shandong) pilot Free Trade Zone, Qingdao, Shandong Patentee after: CAOS industrial Intelligence Research Institute (Qingdao) Co.,Ltd. Country or region after: China Patentee after: Kaos Digital Technology (Qingdao) Co.,Ltd. Patentee after: Karos IoT Technology Co.,Ltd. Address before: 266500 No. 1, Minshan Road, Qingdao area, China (Shandong) pilot Free Trade Zone, Qingdao, Shandong Patentee before: CAOS industrial Intelligence Research Institute (Qingdao) Co.,Ltd. Country or region before: China Patentee before: Haier digital technology (Qingdao) Co.,Ltd. Patentee before: Haier Kaos IOT Technology Co.,Ltd. Address after: 266500 No. 1, Minshan Road, Qingdao area, China (Shandong) pilot Free Trade Zone, Qingdao, Shandong Patentee after: CAOS industrial Intelligence Research Institute (Qingdao) Co.,Ltd. Country or region after: China Patentee after: Haier digital technology (Qingdao) Co.,Ltd. Patentee after: Haier Kaos IOT Technology Co.,Ltd. Address before: 266500 No. 1, Minshan Road, Qingdao area, China (Shandong) pilot Free Trade Zone, Qingdao, Shandong Patentee before: CAOS industrial Intelligence Research Institute (Qingdao) Co.,Ltd. Country or region before: China Patentee before: Haier digital technology (Qingdao) Co.,Ltd. Patentee before: Haier CAOS IOT Ecological Technology Co.,Ltd. |
|
| CP03 | Change of name, title or address |