1. A system, comprising:
a receiving module to receive a request to load a component;
a stack to record the request;
a loader to fulfill the request, wherein when the request has been fulfilled the request is removed from the stack and when the loading of the component is unsuccessful, contents of the stack are made available to a user to indicate the unsuccessfully loaded component.
2. The system according to claim 1, further comprising:
an execution module to execute instructions contained in a component object, wherein the component object is created from information in the component.
3. The system according to claim 1, wherein the receiving module, the stack and the loader reside on a development platform.
4. The system according to claim 1, wherein the receiving module, the stack and the loader reside on an embedded device.
5. The system according to claim 4, wherein the component resides external to the embedded device.
6. The system according to claim 1, wherein the loader includes a plurality of loading modules in a hierarchical relationship and the component is loaded by a highest level loading module capable of loading the component.
7. The system according to claim 1, wherein the stack contents are made available to the user via one of an on-screen display, a printout and a file.
8. A method of loading, comprising the steps of:
receiving a request to load a first software module;
placing a representation of the first software module onto a stack;
determining if the first software module is dependent on a second software module;
placing, when the first software module is dependent on the second software module, a representation of the second software module onto the stack;
loading the second software module;
removing the representation of the second software module from the stack when the second software module has been successfully loaded;
loading the first software module;
removing the representation of the first software module from the stack when the first software module has been successfully loaded; and
making contents of the stack available to a user when the loading of one of the first software module and the second software module has been unsuccessful.
9. The method according to claim 8, wherein the stack contents are made available to the user via one of an on-screen display, a printout and a file.
10. The method according to claim 8, wherein the representation of the first software module is the name of the first software module.
11. A system comprising:
a stack to record a load request for a software component; and
a loader to receive and fulfill the load request for the software component, wherein the loader pushes a representation of the software component onto the stack when the load request is received and pops the representation of the software component off of the stack when the load request has been successfully fulfilled, wherein contents of the stack are made available to a user when fulfillment of the load request has been unsuccessful.
12. The system according to claim 11, further comprising:
an execution module to execute instructions contained in a component object, wherein the component object is created from information in the software component.
13. The system according to claim 11, wherein, when the software component in the load request is dependent on an component, an additional load request for the additional software component is received by the loader and the loader pushes a representation of the additional software component onto the stack when the additional load request is received and pops the representation of the additional software component off of the stack when the additional load request has been successfully fulfilled.
14. The system according to claim 13, wherein contents of the stack are made available to a user when fulfillment of the additional load request has been unsuccessful and the contents of the stack include the representation of the software component and the additional software component.
15. A method of loading a Java class, comprising the steps of:
receiving a request to load a first Java class;
placing a representation of the first Java class onto a stack;
determining if the first Java class is dependent on a second Java class;
placing, when the first Java class is dependent on the second Java class, a representation of the second Java class onto the stack;
loading the second Java class;
removing the representation of the second Java class from the stack when the second Java class has been successfully loaded;
loading the first Java class;
removing the representation of the first Java class from the stack when the first Java class has been successfully loaded; and
making contents of the stack available to a user when the loading of one of the first Java class and the second Java class has been unsuccessful.
16. The method according to claim 15, wherein the stack contents are made available to the user via one of an on-screen display, a printout and a file.
17. The method according to claim 15, wherein the loading steps, the placing steps and the removing steps are performed by a Java class loader.
18. The method according to claim 15, further comprising the steps of:
creating a first Java class object from the loaded first Java class; and
executing instructions included in the first Java class object.
19. The method according to claim 18, wherein the executing step is performed by a Java Virtual Machine.
20. A system, comprising:
a stack to record a load request for a Java class;
a Java class loader to receive and fulfill the load request for the Java class, wherein the loader pushes a representation of the Java class onto the stack when the load request is received and pops the representation of the Java class off of the stack when the load request has been successfully fulfilled, wherein contents of the stack are made available to a user when fulfillment of the load request has been unsuccessful; and
a Java Virtual Machine to execute instructions contained in a Java class object, wherein the Java class object is created from information in the Java class.
21. The system according to claim 20, wherein the Java class loader is one of a custom class loader and a default loader.
22. The system according to claim 20, wherein the stack, the Java class loader and the Java Virtual Machine reside on a development platform.
23. The system according to claim 20, wherein the stack, the Java class loader and the Java Virtual Machine reside on an embedded device.
24. The system according to claim 23, wherein the load request is received via a uniform resource locator.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for storing webpage access records, comprising:
detecting a location of each webpage in a website and historical access number of a user accessing each webpage;
determining an information entropy of each webpage accessed by the user according to the location of each webpage in the website and the historical access number of the user accessing each webpage;
comparing the information entropy of each webpage with a preset threshold value; and
keeping access records of webpages whose information entropies are greater than the preset threshold value.
2. The method of claim 1, wherein the determining an information entropy of each webpage accessed by the user, comprises:
determining an initial entropy of each webpage according to the location of each webpage in the website;
multiplying the historical access number of the user for accessing each webpage with the initial entropy of each webpage to determine the information entropy of each webpage.
3. The method of claim 1, wherein the determining an initial entropy of each webpage according to the location of each webpage in the website, comprises:
according to a uniform resource locator (URL) of each webpage, determining that each webpage is a N-level page of the website; wherein N is an integer greater than or equal to 1;
determining that the initial entropy of each webpage is a preset N-level initial entropy; wherein the N-level initial entropy is greater than a (N+1)-level initial entropy.
4. The method of claim 1, wherein the keeping access records of webpages whose information entropies are greater than the preset threshold value, comprises:
keeping the access records of the webpages whose information entropies are greater than the preset threshold value, upon a condition that a number of webpages accessed by the user reaches a preset number.
5. The method of claim 1, wherein the keeping access records of webpages whose information entropies are greater than the preset threshold value, comprises:
keeping the access records of the webpages whose information entropies are greater than the preset threshold value, upon a condition that a cache of webpages accessed by the user reaches a preset capacity.
6. An apparatus for storing webpage access records, comprising:
an information entropy obtaining unit, configured to determine an information entropy of each webpage accessed by a user according to location of each webpage in a website and historical access number of the user for each webpage;
a cache unit configured to keep access records of webpages whose information entropies are greater than a preset threshold value.
7. The apparatus of claim 6, wherein the information entropy obtaining unit comprises:
an initial entropy determination subunit configured to determine an initial entropy of each webpage according to the location of each webpage in the website;
an information entropy determination subunit configured to multiply the historical access number of the user for accessing each webpage with the initial entropy of each webpage to determine the information entropy of each webpage.
8. The apparatus of claim 6, wherein the initial entropy determination subunit comprises:
a first determination subunit configured to, according to a uniform resource locator (URL) of each webpage, determine that each webpage is a N-level page of the website; wherein N is an integer greater than or equal to 1;
a second determination subunit configured to determine that the initial entropy of each webpage is a preset N-level initial entropy; wherein the N-level initial entropy is greater than a (N+1)-level initial entropy.
9. The apparatus of claim 6, wherein the cache unit is specifically configured to keep the access records of the webpages whose information entropies are greater than the preset threshold value, upon a condition that a number of webpages accessed by the user reaches a preset number.
10. The apparatus of claim 6, wherein the cache unit is specifically configured to keep the access records of the webpages whose information entropies are greater than the preset threshold value, upon a condition that a cache of webpages accessed by the user reaches a preset capacity.
11. A non-transitory computer-readable storage medium comprising a set of instructions for performing a method for storing webpage access records, the set of instructions to direct at least one processor to perform acts of:
obtaining an information entropy of each webpage accessed by a user;
determining whether a number of webpages accessed by the user reaches a preset number or a cache of the webpages accessed by the user reaches a preset capacity;
if the number of the webpages accessed by the user reaches the preset number or the cache of the webpages accessed by the user reaches the preset capacity, keeping access records of webpages whose information entropies are greater than a preset threshold value;
if the number of the webpages accessed by the user does not reaches the preset number and the cache of the webpages accessed by the user does not reaches the preset capacity, keeping all access records of the webpages accessed by the user.
12. The non-transitory computer-readable storage medium of claim 11, wherein the information entropy is determined according to location of each webpage in a website and historical access number of the user for each webpage.