CN102810065B - For the method and system of loader module - Google Patents
For the method and system of loader module Download PDFInfo
- Publication number
- CN102810065B CN102810065B CN201110144285.2A CN201110144285A CN102810065B CN 102810065 B CN102810065 B CN 102810065B CN 201110144285 A CN201110144285 A CN 201110144285A CN 102810065 B CN102810065 B CN 102810065B
- Authority
- CN
- China
- Prior art keywords
- module
- loaded
- program
- root
- root module
- 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.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present invention relates to application program process field.More specifically, the invention particularly relates in application programs the method and system that the program module with hierarchical relationship carries out loading.The invention provides a kind of method for loading the program module with hierarchical relationship, comprising: the request receiving the loader module from client, in described request, comprise the root module information in program to be loaded module; According to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded; And the submodule of described root module and described root module is sent to described client.
Description
Technical field
Application program process field.More specifically, the invention particularly relates in application programs the method and system that the program module with hierarchical relationship carries out loading.
Background technology
Along with the scale of computer applied algorithm, size of code are day by day huge and the continuous lifting of program modularity degree, the existing by reference versatility code of increasing application developer (such as general-purpose library file CommonLibrary) avoids the programing work of repeatability.These codes with reusability may comprise program class Class and other code packages, and they are assembly or the module of a formation application program.A large-scale application program may be made up of multiple such program module, and often there is not person's hierarchical relationship (dependence that also can be regarded as set membership or call) between these program modules.At present a lot of application program developing, test or when running, need by Internet Transmission/call/load these reusable numerous program assembly or modules that there is hierarchical relationship.
Several technical scheme by network transmission program module below current existence.The first loads whole library file (Library).Because library file is usually bulky, and really need to call the part of module in fact just in library file, therefore loading whole library file can cause unnecessary content delivery, extends the time of loading.
The second technical scheme of the prior art only loads required code unit.Such as, micro-WidgetA of client needs 100 code packages in certain library file, and micro-WidgetB of client needs in this library file 50 code packages (wherein have some code packages identical with the code packages of WidgetA needs), although WidgetA and B all can transmit code packages needed for it by a request server end in the process of transmission, and also can avoid transmitting identical code packages, code content transmission that is unnecessary and that repeat can be avoided, but because WidgetA and B needs to send a request (request) to each code packages needed for it to server, cause the increasing number of network request, greatly can extend the time of loading equally.
The third technical scheme of the prior art the code packages required for application (such as Widget) different for client is packed in advance by application developer, then directly packed routine package is sent to client when each Widget calls.The benefit of this technical scheme can avoid loading whole library file, also too much network request can be avoided, but shortcoming possible have the code packages of a large amount of repetitions to be sent to client, because the code packages required for the WidgetA of client and the code packages required for WidgetB exist repeat, when loose coupling (Loose-Coupling) program development, (loose coupling refers to that a certain application program exists multiple developer, the developer of such as WidgetA and the developer of WidgetB do not know inside Widget that the other side develops each other the need of calling identical code packages), which code packages different program developers cannot know in advance is repetition.
Summary of the invention
Consider above-mentioned Problems existing, an object of the present invention is to provide a kind of method or the system that can load the program module with hierarchical relationship in the case of loose coupling.Another object of the present invention is that providing a kind of can load the program module with hierarchical relationship in the case of loose coupling, and duplicated code can be avoided to transmit.Another object of the present invention is that providing a kind of can load the program module with hierarchical relationship in the case of loose coupling, and can avoid unnecessary code transfer.Another object of the present invention is that providing a kind of can load the program module with hierarchical relationship in the case of loose coupling, and can avoid network request that is a large amount of or complexity.Above-mentioned four sub-objects are independent of one another, and goal of the invention of the present invention is not really wanted to reach above-mentioned four sub-objects simultaneously, but only may realize the combination of one of object or any amount.
According to an aspect of the present invention, providing a kind of method for loading the program module with hierarchical relationship, comprising: the request receiving the loader module from client, in described request, comprise the root module information in program to be loaded module; According to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded; And the submodule of described root module and described root module is sent to described client.
According to one embodiment of present invention, said method also comprises: receive the notice about the program module loaded from client, comprises the root module information in the program module loaded in described notice; And according to the root module information in described notice, obtain the submodule information of root module and the described root module loaded loaded.
According to a further aspect in the invention, provide a kind of system for loading the program module with hierarchical relationship, comprise: request receiving device, be configured to receive the request from the loader module of client, in described request, comprise the root module information in program to be loaded module; First acquisition device, is configured to, according to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded; And charger, be configured to the submodule of described root module and described root module to be sent to described client.
According to one embodiment of present invention, said system also comprises: notice receiving trap, is configured to receive the notice about the program module loaded from client, comprises the root module information in the program module loaded in described notice; And second acquisition device, be configured to according to the root module information in described notice, obtain the submodule information of root module and the described root module loaded loaded.
By method and system of the present invention, the program module with hierarchical relationship can be loaded in the case of loose coupling, and duplicated code can be avoided to transmit and/or avoid unnecessary code transfer and/or avoid a large amount of network requests.
Accompanying drawing explanation
By being described in detail to embodiment shown by reference to the accompanying drawings, above-mentioned and other features of the present invention will be more obvious, and label identical in accompanying drawing of the present invention represents same or analogous parts.In the accompanying drawings,
Fig. 1 shows the block diagram of the exemplary computer system 100 be suitable for for realizing embodiment of the present invention;
Fig. 2 shows according to an embodiment of the invention for loading the process flow diagram of the method for the program module with hierarchical relationship;
Fig. 3 A shows the process flow diagram of the method for loading the program module with hierarchical relationship according to further embodiment of this invention;
Fig. 3 B shows the hierarchical relationship figure by client-requested loader module according to the present invention's specific embodiment;
Fig. 4 shows according to an embodiment of the invention for loading the block diagram of the system of the program module with hierarchical relationship;
Fig. 5 shows according to an embodiment of the invention for loading the block diagram of the system of the program module with hierarchical relationship.
Embodiment
Hereinafter, the method and system for loading the program module with hierarchical relationship provided by the invention is described in detail by embodiment with reference to accompanying drawing.
Fig. 1 shows the block diagram of the exemplary computer system 100 be suitable for for realizing embodiment of the present invention.As shown, computer system 100 can comprise: CPU (CPU (central processing unit)) 101, RAM (random access memory) 102, ROM (ROM (read-only memory)) 103, system bus 104, hard disk controller 105, keyboard controller 106, serial interface controller 107, parallel interface controller 108, display controller 109, hard disk 110, keyboard 111, serial peripheral equipment 112, concurrent peripheral equipment 113 and display 114.In such devices, what be coupled with system bus 104 has CPU101, RAM102, ROM103, hard disk controller 105, keyboard controller 106, serialization controller 107, parallel controller 108 and display controller 109.Hard disk 110 is coupled with hard disk controller 105, keyboard 111 is coupled with keyboard controller 106, serial peripheral equipment 112 is coupled with serial interface controller 107, and concurrent peripheral equipment 113 is coupled with parallel interface controller 108, and display 114 is coupled with display controller 109.Should be appreciated that the structured flowchart described in Fig. 1 illustrates just to the object of example, instead of limitation of the scope of the invention.In some cases, can increase or reduce some equipment as the case may be.
Fig. 2 shows according to an embodiment of the invention for loading the process flow diagram of the method for the program module with hierarchical relationship.
Method shown in Fig. 2, from step 201, in step 201, receives the request of the loader module from client, comprises the root module information in program to be loaded module in described request.Here the client of indication is a concept relative to server end, can be the computing machine etc. of Client Agent, browser, micro-Widget, application developer's request of loading program module in exploitation, test process, and not necessarily is terminal user.In a word, any soft and hardware such as application, plug-in unit, computing machine sending loader module request all can be understood to the client of indication here.
According to one embodiment of present invention, the root module information in program to be loaded module is only comprised in the request of loader module.According to still another embodiment of the invention, the submodule information of root module information in program to be loaded module and part or all of this root module is comprised in the request of loader module.If only comprise the root module information in program to be loaded module in the request of loader module, all submodules of this root module can be obtained according to the hierarchical relationship information between root module information and program module.If the submodule information of the root module information comprised in the request of loader module in program to be loaded module and partly or entirely this root module; although there is the process of part replicate analysis, all submodules obtaining this root module still can be guaranteed.Certainly, client to obtain hierarchical relationship between the program module that not yet loads, therefore client is when sending request, if program module to be loaded is not yet loaded on client, client does not know in these program modules to be loaded which is root module, which is submodule, therefore only may comprise root module in its request, also not only may comprise root module but also comprise submodule.In any case but, root module be bound to comprise in the request (because if a module is that client needs load and are not yet loaded, and do not have other to need the module loaded to depend on this module, so this module is root module, and is bound to be included in the request of client transmission).
It is pointed out that there is hierarchical relationship program module between exist and to call and called, or to rely on and by the relation relied on.Therefore, in the present invention, only will depend on other program module and not the program module that relies on by other program module be called root module (the most top module), the program module relied on by root module is called submodule.The relation of root module and submodule can be interpreted as the relation of root node in tree derivation and child node simply.Also it is to be noted, the information loading one or more root module may be comprised in request from a loader module of client, such as client-requested loads two program modules, not there is hierarchical relationship each other between these two program modules, and for this client, need the program module (needing the program module loaded not comprise the program module be loaded) loaded to depend on this two modules without any other, so these two program modules are root module.
According to one embodiment of present invention, the program module in the present invention is one or more in reusable code packages, code unit, code components, program class Class.It will be appreciated by those skilled in the art that the concept of program module it is emphasised that unit, the part of configuration program, it may be presented as different forms under different programmed environments.According to one embodiment of present invention, the program module with hierarchical relationship in the present invention is the modules of source code without compiling.According to still another embodiment of the invention, the program module with hierarchical relationship in the present invention is object code (binary code) module through compiling.It will be appreciated by those skilled in the art that no matter program module is source code or object code, as long as they also exist hierarchical relationship information each other just can be applied to the present invention.
Next, the side 6 shown in Fig. 2 proceeds to step 202, in step 202., according to the root module information in described request, obtains the submodule of described root module to be loaded and described root module to be loaded.Why can obtain root module to be loaded and submodule thereof according to the root module information in request, be because the hierarchical relationship information between program module is acquired.According to one embodiment of present invention, by analyzing each program module successively, obtain the hierarchical relationship information between all program modules.According to another embodiment of the present invention, in response to the request of the described loader module from client, obtain the hierarchical relationship information between program module to be loaded.According to one more embodiment of the present invention, obtain the hierarchical relationship information between program module to be loaded by the input of application developer.Hierarchical relationship information between the program module that utilization has obtained and the root module information in program module load request, the one-level submodule of root module to be loaded can be analyzed, and the submodule of one-level submodule, by that analogy, thus determine all program module information with hierarchical relationship to be loaded, and and then obtain the program module with hierarchical relationship to be loaded.It will be understood by those skilled in the art that hierarchical relationship information can obtain in several ways, the three kinds of embodiments above provided are only the objects of exemplary illustration, do not form any restriction to embodiment.
Next in step 206, the submodule of described root module and described root module is sent to described client.Like this, client just can realize the loading to all program to be loaded modules.According to one embodiment of present invention, the request receiving in step 201 and the module in step 206 are sent and are all undertaken by Ethernet or other network.
By the method shown in Fig. 2, be different from prior art, client only can inform the root module information of program to be loaded module when sending the request of loader module, and by only sending load request, (and load request is very simple, only comprise root module information) just complete loading (and being only loaded with the required program module of client) to all modules to be loaded, thus achieve the object that the present invention avoids transmitting unnecessary code content and avoiding complicated network request.
Fig. 3 A shows the process flow diagram of the method for loading the program module with hierarchical relationship according to further embodiment of this invention.
Step 301 in method shown in Fig. 3 A and 302 corresponds respectively to the step 201 and 202 in the method shown in Fig. 2, does not repeat them here.In step 303, receive the notice about the program module loaded from client, in described notice, comprise the root module information in the program module loaded.Due in loading procedure before (micro-Widget of another request of loading program module of such as client or other plug-in unit), there are some program modules may be loaded into client, in order to avoid repeating to load identical program module, preferably, client can notify the program module information that loaded in current program module to be loaded.According to one embodiment of present invention, about the root module information only comprised in the notice of the program module loaded in the program module loaded.This is because, although a lot of program module may be had to be loaded, for the object of simplified network request (notice also can be classified as the one of network request in essence), also there is hierarchical relationship due between the program module that loaded, therefore client has established the hierarchical relationship between the program module that loaded, and only notifies the root module in the program module loaded.According to one embodiment of present invention, hierarchical relationship between the program module that loaded in local maintenance of client (such as by constructing and safeguarding the mode of a local global variable).
Next, in step 304, according to the root module information in described notice, the submodule information of root module and the described root module loaded loaded is obtained.Step 304 is similar to step 202, does not repeat them here.Step 304 is with the difference of step 202: the root module needing actual acquisition to be loaded in step 202 and submodule thereof, and in step 304, only need the information obtaining root module and the submodule thereof loaded, the root module and submodule thereof that have loaded is obtained without the need to reality.
In step 305, from the submodule of obtained root module and described root module, loaded root module and all submodules is deleted.In order to avoid the program module loaded is loaded again, these program modules loaded are deleted from program module to be loaded.Next, within step 306, the residual program module after the deleted root module that loaded and all submodules thereof is sent to described client.Step 306 can be understood as corresponding to the step 206 in Fig. 2, and its essence is all the module to be loaded being transmitted through the network to client that needs finally determined to be sent to client.
Although it is pointed out that set by having the order of step 301-306 in Fig. 3 and text description above, may there is multiple change in the relation between the execution sequence of step 301-306 or step without departing from the inventive concept of the premise.According to one embodiment of present invention, in the request of the loader module received in step 301 except the root module information of program module to be loaded, the notice about the program module loaded also is comprised.That is, the notice in step 303 and the request in step 301 can be sent by client simultaneously.According to one embodiment of present invention, first can perform step 304, according to the root module information in described notice, obtain the submodule information of root module and the described root module loaded loaded.Then perform step 302, according to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded.Due to before execution step 302, which known program module to be loaded, therefore when performing step 302, just only can obtain the program module be not loaded in program to be loaded module, that is, therefrom delete without the need to first obtaining whole program to be loaded modules the program module loaded again, but just determine the program to be loaded module needing final transmission in the analysis level relation information stage.Like this, step 305 is also without the need to again performing.In a word, the order between the step in Fig. 2 and Fig. 3 is only exemplary explanation, and is not construed as limiting the invention.
By the method shown in Fig. 3 A, be different from prior art, client only can inform the root module information of program to be loaded module when sending the request of loader module, and notify which program module is loaded (only notifying the root module of loader module during notice), (and load request is very simple only to send a load request and notice, only comprise root module information) just complete loading to all modules to be loaded (and be only loaded with client required and the program module be not yet loaded), thus achieve the present invention and avoid transmitting unnecessary code content, avoid transmitting the code content repeated and the object avoiding complicated network request, time delay when greatly saving the network bandwidth and load multiple program module.
Method shown in Fig. 2 and Fig. 3 A also has a technique effect especially obvious under HTTP request.In order to meet the Catch characteristic of HTTP request, the Get in HTTP request must be used to ask (in Get request, only comprising URL address), and the Post request (comprise a lot of parameter information in Post request, Catch characteristic can not be met) during HPPT can not be used to ask.But, (concrete URL address) usually when client-requested loads a large amount of program module, cannot be asked required all program modules to be loaded one by one by Get.Benefit of the present invention is just: only comprise root module in request, and does not comprise the information of other module, Get can be utilized to ask to send the request of loader module, thus can meet Catch characteristic.Particular content about Catch characteristic belongs to the common practise of this area, does not repeat them here.
Below in conjunction with the method shown in Fig. 2 and Fig. 3 A, by a simple example, the method for loading the program module with hierarchical relationship provided by the invention is described.Fig. 3 B shows the hierarchical relationship figure between program module.Supposing to have two micro-in client browser, is WidgetA and WidgetB respectively.Incipient stage, client is without any the program module loaded.Present WidgetA request of loading class ClassA (ClassA is program module), and ClassA comprises subclass (submodule) A0 and B0, and A0 comprises subclass A1 further, and B0 comprises subclass B1 further.So WidgetA only sends the request of request of loading ClassA (root module) to server end.When after received server-side to this request, utilize the hierarchical relationship information between program module and the root module information in request, obtain ClassA and its whole four subclass A0, A1, B0, B1, and be sent to client by after these five class packings, thus complete the load request of WidgetA.
Next, suppose another micro-WidgetB request of loading class ClassB of same client, and ClassB comprises subclass (submodule) B0 and C0, and class B0 comprises subclass B1, so WidgetB sends the request (only comprising root class ClassB in request) loading ClassB to server end, and announcement server end class ClassB0 is loaded (only comprising root class ClassB0 in notice).Server is after the request receiving WidgetB transmission and notice, namely determine: the class that WidgetB will load is ClassB, B0, B1, C0, and ClassB0 and B1 has been loaded, therefore server end only obtains ClassB and ClassC0, and be sent to client by after these two program class packings, thus complete the request of the loader module of WidgetB.
Fig. 4 shows according to an embodiment of the invention for loading the block diagram of the system of the program module with hierarchical relationship.System shown in Fig. 4 is represented by system 400 on the whole.Particularly, system 400 comprises request receiving device 401, is configured to receive the request from the loader module of client, comprises the root module information in program to be loaded module in described request; First acquisition device 402, is configured to, according to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded; And charger 406, be configured to the submodule of described root module and described root module to be sent to described client.The device 401,402 and 406 that it will be appreciated by those skilled in the art that in system 400 corresponds respectively to the step 201,202 and 206 in the method shown in Fig. 2, does not repeat them here.
Fig. 5 shows according to an embodiment of the invention for loading the block diagram of the system of the program module with hierarchical relationship.System shown in Fig. 5 is represented by system 500 on the whole.Particularly, system 500 comprises request receiving device 501, is configured to receive the request from the loader module of client, comprises the root module information in program to be loaded module in described request; First acquisition device 502, is configured to, according to the root module information in described request, obtain the submodule of described root module to be loaded and described root module to be loaded; Notice receiving trap 503, is configured to receive the notice about the program module loaded from client, comprises the root module information in the program module loaded in described notice; Second acquisition device 504, is configured to according to the root module information in described notice, obtains the submodule information of root module and the described root module loaded loaded; Delete device 505, is configured to delete the root module and all submodules thereof that have loaded from the submodule of obtained root module and described root module; And charger 506, be configured to the submodule of described root module and described root module to be sent to described client.The device 501-506 that it will be appreciated by those skilled in the art that in system 500 corresponds respectively to the step 301-306 in the method shown in Fig. 3, does not repeat them here.
Process flow diagram in accompanying drawing and block diagram, illustrate according to the architectural framework in the cards of the system of various embodiments of the invention, method and computer program product, function and operation.In this, each square frame in process flow diagram or block diagram can represent a part for module, program segment or a code, and a part for described module, program segment or code comprises one or more executable instruction for realizing the logic function specified.Also it should be noted that at some as in the realization of replacing, the function marked in square frame also can be different from occurring in sequence of marking in accompanying drawing.Such as, in fact the square frame that two adjoining lands represent can perform substantially concurrently, and they also can perform by contrary order sometimes, and this determines according to involved function.Also it should be noted that, the combination of the square frame in each square frame in block diagram and/or process flow diagram and block diagram and/or process flow diagram, can realize by the special hardware based system of the function put rules into practice or operation, or can realize with the combination of specialized hardware and computer instruction.
Although more than in conjunction with instantiation, be described in detail the system and method for remote application process local file that utilizes of the present invention, the present invention is not limited to this.Those of ordinary skill in the art can carry out multiple conversion, substitutions and modifications and without departing from the spirit and scope of the present invention to the present invention under instructions instruction.Should be appreciated that, all such changes, replacement, amendment still fall within protection scope of the present invention.Protection scope of the present invention is limited by claims.
Claims (16)
1., for loading a method for the program module with hierarchical relationship, comprising:
Receive the request from the loader module of client, in described request, comprise the root module information in program to be loaded module;
According to the root module information in described request, obtain the submodule of root module to be loaded and described root module to be loaded; And
The submodule of described root module and described root module is sent to described client, and wherein, according to the root module information in described request, the submodule obtaining root module to be loaded and described root module to be loaded comprises:
According to the root module information in described request and the hierarchical relationship between program module, obtain all submodules of described root module to be loaded and described root module to be loaded, what wherein hierarchical relationship referred to exist between program module calls and invoked relation.
2. the method for claim 1, also comprises:
Delete the root module and all submodules thereof that have loaded in the submodule of root module and the root module obtained; Further,
Wherein the submodule of described root module and described root module is sent to described client to comprise:
Residual program module after deleting the root module that loaded and all submodules thereof is sent to described client.
3. method as claimed in claim 2, also comprises:
Receive the notice about the program module loaded from client, in described notice, comprise the root module information in the program module loaded; And
According to the root module information in described notice, obtain the submodule information of root module and the described root module loaded loaded.
4. method as claimed in claim 3, wherein
According to the root module information in described notice, the submodule information obtaining root module and the described root module loaded loaded comprises:
According to the root module information in described notice and the hierarchical relationship between program module, all submodule information of the root module loaded described in acquisition and the described root module loaded.
5. the method as described in as arbitrary in claim 1-4, also comprises:
By analyzing each program module successively, obtain the hierarchical relationship information between all program modules.
6. the method as described in as arbitrary in claim 1-4, also comprises:
In response to the request of the described loader module from client, obtain the hierarchical relationship information between program module to be loaded.
7. the method for claim 1, wherein program module is program class Class, and described in there is hierarchical relationship program module between be loose coupling.
8. the method as described in as arbitrary in claim 3 or 4, only comprises the root module information in program to be loaded module, and only comprises the root module information in the program module loaded in described notice in wherein said request.
9., for loading a system for the program module with hierarchical relationship, comprising:
Request receiving device, is configured to receive the request from the loader module of client, comprises the root module information in program to be loaded module in described request;
First acquisition device, is configured to, according to the root module information in described request, obtain the submodule of root module to be loaded and described root module to be loaded; And
Charger, be configured to the submodule of described root module and described root module to be sent to described client, wherein the first acquisition device is further configured to:
According to the root module information in described request and the hierarchical relationship between program module, obtain all submodules of root module to be loaded and described root module to be loaded, what wherein hierarchical relationship referred to exist between program module calls and invoked relation.
10. system as claimed in claim 9, also comprises:
Delete device, is configured to delete the root module loaded in the submodule of root module and the described root module obtained and all submodules thereof; Further,
Wherein charger is further configured to:
Residual program module after deleting the root module that loaded and all submodules thereof is sent to described client.
11. systems as claimed in claim 10, also comprise:
Notice receiving trap, is configured to receive the notice about the program module loaded from client, comprises the root module information in the program module loaded in described notice; And
Second acquisition device, is configured to according to the root module information in described notice, obtains the submodule information of root module and the described root module loaded loaded.
12. systems as claimed in claim 11, wherein the second acquisition device is further configured to:
According to the root module information in described notice and the hierarchical relationship between program module, all submodule information of the root module loaded described in acquisition and the described root module loaded.
13. as arbitrary in claim 9-12 as described in system, also comprise:
3rd acquisition device, is configured to, by analyzing each program module successively, obtain the hierarchical relationship information between all program modules.
14. as arbitrary in claim 9-12 as described in system, also comprise:
3rd acquisition device, is configured to the request in response to the described loader module from client, obtains the hierarchical relationship information between program module to be loaded.
15. systems as claimed in claim 9, wherein program module is program class Class, and described in there is hierarchical relationship program module between be loose coupling.
16. as arbitrary in claim 11 or 12 as described in system, only comprise the root module information in program to be loaded module in wherein said request, and in described notice, only comprise the root module information in the program module loaded.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110144285.2A CN102810065B (en) | 2011-05-31 | 2011-05-31 | For the method and system of loader module |
| US13/484,388 US9146753B2 (en) | 2011-05-31 | 2012-05-31 | Loading program modules |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110144285.2A CN102810065B (en) | 2011-05-31 | 2011-05-31 | For the method and system of loader module |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102810065A CN102810065A (en) | 2012-12-05 |
| CN102810065B true CN102810065B (en) | 2016-04-27 |
Family
ID=47233774
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110144285.2A Expired - Fee Related CN102810065B (en) | 2011-05-31 | 2011-05-31 | For the method and system of loader module |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US9146753B2 (en) |
| CN (1) | CN102810065B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105094857B (en) * | 2014-04-23 | 2018-09-25 | 国际商业机器公司 | Method and system for application load |
| CN106919812B (en) * | 2015-12-26 | 2020-06-16 | 腾讯科技（深圳）有限公司 | Application process authority management method and device |
| CN107506483A (en) * | 2017-09-15 | 2017-12-22 | 广州优视网络科技有限公司 | Page loading method, device, electronic equipment and storage medium |
| CN112486481B (en) * | 2020-12-03 | 2024-03-19 | 北京展心展力信息科技有限公司 | Multi-module layered architecture implementation method and device, electronic equipment and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6559871B1 (en) * | 1999-09-29 | 2003-05-06 | International Business Machines Corporation | Asynchronous tree navigator graphical user interface and associated methods |
| CN101493775A (en) * | 2009-03-06 | 2009-07-29 | 北京北纬通信科技股份有限公司 | Dynamic loading system and loading method thereof for embedded system |
| CN101937353A (en) * | 2010-09-20 | 2011-01-05 | 中兴通讯股份有限公司 | Method and device for deploying and loading plug-in unit |
Family Cites Families (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2256417A1 (en) | 1996-05-24 | 1997-11-27 | Gregory T. White | Computer method and apparatus for object streaming |
| US5966702A (en) | 1997-10-31 | 1999-10-12 | Sun Microsystems, Inc. | Method and apparatus for pre-processing and packaging class files |
| US6230184B1 (en) * | 1998-10-19 | 2001-05-08 | Sun Microsystems, Inc. | Method and apparatus for automatically optimizing execution of a computer program |
| US20040015953A1 (en) | 2001-03-19 | 2004-01-22 | Vincent Jonathan M. | Automatically updating software components across network as needed |
| US7389515B1 (en) | 2001-05-21 | 2008-06-17 | Microsoft Corporation | Application deflation system and method |
| US6901589B2 (en) * | 2001-06-25 | 2005-05-31 | Wind River Systems, Inc. | System and method for determining a root cause of a failure |
| US7178140B2 (en) | 2002-02-28 | 2007-02-13 | Sun Microsystems, Inc. | Speeding up application downloading from a remote server |
| US20070288556A1 (en) * | 2002-05-17 | 2007-12-13 | Anton Richard N | System and Method for Encoding and Decoding Data Files |
| US20040255294A1 (en) * | 2003-02-12 | 2004-12-16 | Bea Systems, Inc. | System and method for hierarchical loading of EJB implementations |
| GB0326915D0 (en) * | 2003-11-19 | 2003-12-24 | Ibm | A method and system for updating/reloading the content of pages browsed over a network |
| US7644402B1 (en) * | 2004-03-17 | 2010-01-05 | Sun Microsystems, Inc. | Method for sharing runtime representation of software components across component loaders |
| US7937717B2 (en) | 2004-09-13 | 2011-05-03 | Tvworks, Llc | Method and apparatus enabling multiple application sharing of classes |
| CN101193113A (en) * | 2006-11-29 | 2008-06-04 | 国际商业机器公司 | Content response and content request method and content responder and content requester |
| US10216854B2 (en) * | 2007-07-26 | 2019-02-26 | International Business Machines Corporation | Optimized page script downloads in a component based architecture |
| US20090125611A1 (en) * | 2007-11-08 | 2009-05-14 | Barsness Eric L | Sharing loaded java classes among a plurality of nodes |
-
2011
- 2011-05-31 CN CN201110144285.2A patent/CN102810065B/en not_active Expired - Fee Related
-
2012
- 2012-05-31 US US13/484,388 patent/US9146753B2/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6559871B1 (en) * | 1999-09-29 | 2003-05-06 | International Business Machines Corporation | Asynchronous tree navigator graphical user interface and associated methods |
| CN101493775A (en) * | 2009-03-06 | 2009-07-29 | 北京北纬通信科技股份有限公司 | Dynamic loading system and loading method thereof for embedded system |
| CN101937353A (en) * | 2010-09-20 | 2011-01-05 | 中兴通讯股份有限公司 | Method and device for deploying and loading plug-in unit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102810065A (en) | 2012-12-05 |
| US20120311554A1 (en) | 2012-12-06 |
| US9146753B2 (en) | 2015-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102855178B (en) | Method and device for generating Mock base during unit test | |
| CN102810065B (en) | For the method and system of loader module | |
| CN108965375B (en) | Service call proxy control system, method, server and readable storage medium | |
| CN108197024B (en) | Embedded browser debugging method, debugging terminal and computer readable storage medium | |
| US10540150B2 (en) | Composable context menus | |
| CN103345386A (en) | Software production method, device and operation system | |
| US20180025162A1 (en) | Application program analysis apparatus and method | |
| CA2846581A1 (en) | Data infrastructure for providing interconnectivity between platforms, devices and operating systems | |
| US9529572B1 (en) | Composable application session parameters | |
| Mieścicki et al. | Verification of Concurrent Engineering Software Using CSM Models | |
| CN111666572A (en) | Automatic change infiltration test frame | |
| CN114116509A (en) | Program analysis method, program analysis device, electronic device, and storage medium | |
| EP2972880B1 (en) | Kernel functionality checker | |
| CN106293651A (en) | The implementation method of a kind of general-purpose interface and device | |
| CN109408577A (en) | ORACLE database JSON analytic method, system, device and can storage medium | |
| CN111324332A (en) | Big data task processing method and system, electronic device and storage medium | |
| CN104834958A (en) | Method and device for evaluating steps of answer | |
| US9684744B2 (en) | Verification of system assertions in simulation | |
| CN109683879B (en) | Front-end component processing method and device | |
| CN106330556A (en) | Method and device for generating service module calling associated information | |
| CN112685023A (en) | Front-end development processing method, device, equipment and storage medium based on basic library | |
| US9800692B2 (en) | Expression based declarative data service execution chaining | |
| CN112667491A (en) | Function test method and device of virtual machine | |
| CN113703879B (en) | Object reloading method, device, equipment and storage medium | |
| US20230028635A1 (en) | Techniques for managing container-based software services |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160427 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |