CN103425532A - JAVA stateless object management method and device - Google Patents
JAVA stateless object management method and device Download PDFInfo
- Publication number
- CN103425532A CN103425532A CN2013103789715A CN201310378971A CN103425532A CN 103425532 A CN103425532 A CN 103425532A CN 2013103789715 A CN2013103789715 A CN 2013103789715A CN 201310378971 A CN201310378971 A CN 201310378971A CN 103425532 A CN103425532 A CN 103425532A
- Authority
- CN
- China
- Prior art keywords
- stateless
- buffer memory
- allocating
- parameter
- java
- 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.)
- Pending
Links
Images
Landscapes
- Memory System Of A Hierarchy Structure (AREA)
Abstract
The invention relates to the JAVA related technical field, in particular to a JAVA stateless object management method and a JAVA stateless object management device. The management method comprises the steps of starting up an IoC (Inversion of Control) container; instantiating stateless objects, saving the stateless objects in a buffer memory and maintaining object use situation parameters; making a response to an object calling request which contains identifiers of objects to be called; if the stateless objects corresponding to the identifiers of the objects to be called have already been saved in the buffer memory, obtaining the corresponding stateless objects from the buffer memory, feeding back the corresponding stateless objects and updating the object use situation parameters; otherwise, instantiating new stateless objects, deleting the stateless objects which meet deletion rules according to the object use situation parameters corresponding to each stateless object saved in the buffer memory, saving the new objects in the buffer memory and maintaining the corresponding object use situation parameters. By maintaining the object use situation parameters of the stateless objects saved in the buffer memory and deleting the stateless objects which meet the deletion rules, the situation that a great number of stateless objects occupy the buffer memory for a long time is avoided.
Description
Technical field
The present invention relates to the JAVA correlative technology field, particularly a kind of management method and device of JAVA stateless object.
Background technology
In the application of current J2EE (J2EE is Java 2 Platform Enterprise Edition) Enterprise Development, a large amount of IoC (Inversion of Control controls reversion) technology of using, weakened greatly the dependence between object and object, object is by the JavaBean instantiation, (JavaBean is the software assembly model of describing Java, instance object refers to object-instantiated, and be the operation of object storage allocation), dependence between the management of object and object and object is transferred to the IoC container and is in charge of, the IoC container, the default Spring container of JAVA for example, use a configuration file (normally XML), define the title of object on configuration file, how instantiation (Prototype mode or Singleton mode), must set the attribute that becomes certain object etc. after which object-instantiated, after starting container, all objects can directly be taken from the IoC container, need not write any a line program code and produce object, or set up the dependence between object and object.Thereby realized data decoupler, the extensibility that has promoted the maintainable of system and strengthened system.
Be illustrated in figure 1 the process flow diagram that existing IoC technology starts instantiation stateless object process, the stateless object refers to the object without attribute, only comprises method in the class of object, and its detailed process comprises:
Step S101, the IoC container starts;
Step S102, the corresponding object configuration parameter according to the object identity of configuration file, instance object;
Step S103, the initialization object;
Step S104, be positioned over buffer memory by object, and buffer memory can be generally the target cache pond;
Step S105, if there is no the object identity of not instantiation in configuration file, object all generates, finish, otherwise execution step S102.
Be illustrated in figure 2 existing IoC technology and call the process flow diagram of stateless object process, comprising:
Step S201, response comprises the allocating object request for the treatment of the allocating object sign;
Step S202, the stateless object that the retrieve dormant object identity is corresponding from buffer memory;
Step S203 obtains the stateless object that stand-by object identity is corresponding from buffer memory.
From the step of Fig. 1 and Fig. 2, can find out, at present existing IoC technology is that all stateless objects are all generated in the buffer memory (or being called cache pool) that is positioned over internal memory to the management method of stateless object, but some objects that often do not use or seldom use also can be kept in cache pool for a long time, the machine that this is less for internal memory or JVM (Java Virtual Machine, Java Virtual Machine) are no small burdens.And, when the stateless object is too much in system, also likely cause internal memory to overflow.
Summary of the invention
Based on this, be necessary the technical matters that the cache management of stateless object is needed larger internal memory and easily causes internal memory to overflow for prior art, a kind of management method and device of JAVA stateless object is provided.
A kind of management method of JAVA stateless object comprises:
Start the IoC container;
The corresponding object configuration parameter instantiation stateless object according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the corresponding object service condition of each stateless object parameter;
Response comprises the allocating object request for the treatment of the allocating object sign:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the corresponding object configuration parameter instantiation stateless object according to object identity, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
A kind of management devices of JAVA stateless object comprises:
Container starts module, for starting the IoC container;
The target cache module, for the object configuration parameter instantiation stateless object corresponding according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the corresponding object service condition of each stateless object parameter;
The object reference module comprises the allocating object request for the treatment of the allocating object sign for response:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the corresponding object configuration parameter instantiation stateless object according to object identity, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
The present invention is by being kept at the stateless object maintenance object service condition parameter in buffer memory, thereby when the stateless object in buffer memory need to be replaced, can be according to object service condition parameter, deletion meets rejects regular stateless object, thereby avoids a large amount of stateless objects to take for a long time buffer memory.Reduce the internal memory burden of machine, avoid internal memory to overflow.Simultaneously, by the stateless object that is chosen in current time Preset Time section before the least number of times that is called, as meeting, reject regular stateless object, avoided the long-term committed memory of stateless object that does not often use or seldom use.
The accompanying drawing explanation
Fig. 1 is the process flow diagram of existing IoC technology startup instantiation stateless object process;
Fig. 2 calls the process flow diagram of stateless object process for having the IoC technology now;
The workflow diagram of the management method that Fig. 3 is a kind of JAVA stateless of the present invention object;
The specific works flow process figure of step S302 in the workflow diagram of the management method that Fig. 4 is a kind of JAVA stateless of the present invention object;
The IoC that Fig. 5 is an example of the present invention starts the workflow diagram of instantiation stateless object;
The workflow diagram of the stateless object reference that Fig. 6 is an example of the present invention;
The modular structure figure of the management devices that Fig. 7 is a kind of JAVA stateless of the present invention object.
Embodiment
Below in conjunction with the drawings and specific embodiments, the present invention will be further described in detail.
Be illustrated in figure 3 the workflow diagram of the management method of a kind of JAVA stateless of the present invention object, comprise:
Step S301, start the IoC container;
Step S302, the corresponding object configuration parameter instantiation stateless object according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the corresponding object service condition of each stateless object parameter;
Step S303, response comprises the allocating object request for the treatment of the allocating object sign:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the corresponding object configuration parameter instantiation stateless object according to object identity, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
Object identity and corresponding object configuration parameter thereof can leave in configuration file in advance, and specifically, object identity can comprise the title of object.The object configuration parameter can comprise after the mode, which object-instantiated of object-instantiated must set the attribute that becomes certain object etc.
Step S303 wherein, therein in embodiment, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time.For example, meet and reject regular stateless object and can comprise: the N stateless object of least number of times that is called in second before the current time, N is natural number, can design according to actual needs for example N=60, or N=3600 etc.This embodiment can adopt least recently used algorithm (LRU, Least Recently Used algorithm) to realize, specific algorithm can design according to actual needs.
Therein in embodiment, described object service condition parameter comprises the number of times and being called the time for the last time of being called of corresponding stateless object.Can be by setting up stateless object and the object service condition parameter in the associated buffer memory of list, thus service object service condition parameter.In step S303, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding, increase the described number of times that is called for the treatment of that allocating object is corresponding, and upgrade that the time of being called is the current time for the last time.
The total amount that buffer memory is preserved the stateless object can be limited by increasing buffer memory total amount parameter, thereby avoids distributing too much buffer memory, to improve system performance.In embodiment, the total amount that described buffer memory is preserved the stateless object arranges according to default buffer memory total amount parameter therein, and described buffer memory total amount parameter is preserved by default configuration file.The IoC container, when starting, can read various parameters from default configuration file, and by increase buffer memory total amount parameter in configuration file, thereby the total amount that makes buffer memory preserve the stateless object is controlled adjustment, realizes stateless Object Management group flexibly.
When adopting buffer memory total amount parameter, step S302 can make adaptability revision.In embodiment, as shown in Figure 4, step S302 comprises therein:
Object identity reads sub-step S401, and reading object sign and corresponding object configuration parameter from default configuration file, carry out object-instantiated sub-step S402;
Object-instantiated sub-step S402, the corresponding object configuration parameter instantiation stateless object according to object identity, and preserve described stateless parameter in buffer memory, and safeguard the corresponding object service condition of stateless object parameter, carry out object detection sub-step S403;
Object detection sub-step S403, if the total amount of the stateless object of having preserved in buffer memory is less than described buffer memory total amount parameter, and have the object identity of not instantiation in described configuration file, carry out object identity and read sub-step S401, otherwise ending step S302.
Wherein, detecting sub-step S403 has made two kinds of situations stop the instance object sign:
The first situation, when buffer memory is full, the total amount of the stateless object of having preserved in buffer memory is more than or equal to described buffer memory total amount parameter, stops the instance object sign;
The second situation, all instantiations of object identity in configuration file, stop the instance object sign.
When adopting buffer memory total amount parameter, can revise and reject rule.Therein in embodiment, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time, and the stateless object of having preserved in buffer memory adds the above total amount for the treatment of allocating object and is greater than described buffer memory total amount parameter.The present embodiment, make when buffer memory adds the above total amount until allocating object and is less than or equal to buffer memory total amount parameter less than, the stateless object of having preserved in buffer memory, without the stateless object of deleting in buffer memory.In this case because cache maintenance all stateless objects, so now the stateless in buffer memory to as if without replacing.Only full at buffer memory, be that the stateless object preserved in buffer memory is when adding the above total amount until allocating object and being greater than buffer memory total amount parameter, adopt least recently used algorithm, from buffer memory by least-recently-used stateless object, replace with the new allocating object for the treatment of, make at internal memory enough, so in the enough situation of buffer memory capacity, avoid deleting the stateless object in buffer memory, reduce deletion and the reloading number of times of stateless object.
As an example, as shown in Figure 5, for the IoC of an example of the present invention starts the workflow diagram of instantiation stateless object, adopt the target cache pond as the buffer memory of depositing the stateless object, specifically comprise:
Step S501, the IoC container starts;
Step S502, if buffer memory is full, exit flow process, otherwise execution step S503;
Step S503, reading object sign and corresponding object configuration parameter from default configuration file;
Step S504, the corresponding object configuration parameter instantiation stateless object according to object identity;
Step S505, initialization stateless object;
Step S506 preserves the stateless object, and safeguards the corresponding object service condition of stateless object parameter in buffer memory;
Step S507, if the total amount of the stateless object of having preserved in buffer memory is less than described buffer memory total amount parameter, buffer memory less than, perform step S508, otherwise exit flow process;
Step S508, if there is no the object identity of not instantiation in configuration file, object all generates, and exits flow process, otherwise execution step S503.
As shown in Figure 6, be the workflow diagram of the stateless object reference of an example of the present invention, adopt the target cache pond as the buffer memory of depositing the stateless object, specifically comprise:
Step S610, response comprises the allocating object request for the treatment of the allocating object sign;
Step S620, describedly treat that allocating object identifies corresponding stateless object if preserved in buffer memory, execution step S621, otherwise execution step S624;
Step S621 obtains and describedly treats that allocating object identifies corresponding stateless object as treating allocating object from buffer memory;
Step S622, obtain and return the described allocating object for the treatment of;
Step S623, upgrade and treat the object service condition parameter that allocating object is corresponding, exits flow process;
Step S624 obtains and treats that allocating object identifies corresponding object configuration parameter from configuration file, according to obtained object configuration parameter instantiation stateless object;
Step S625, using the stateless object for the treatment of the instantiation of allocating object sign as treating allocating object, obtain and return the described allocating object for the treatment of;
Step S626, obtain the object service condition parameter corresponding to each stateless object of preserving in buffer memory;
Step S627, according to lru algorithm, least-recently-used stateless object in buffer memory is replaced with and treats allocating object, execution step S623, carrying out lru algorithm need to determine according to object service condition parameter, and the renewal of object service condition parameter can adopt the methods such as counting method, chronometry to realize, by these methods, the service condition of sign object, when generating object is replaced, take object service condition parameter as basis, select least-recently-used object and replace.
Be illustrated in figure 7 the modular structure figure of the management devices of a kind of JAVA stateless of the present invention object, comprise:
Container starts module 710, for starting the IoC container;
Target cache module 720, for the object configuration parameter instantiation stateless object corresponding according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the corresponding object service condition of each stateless object parameter;
Object reference module 730 comprises the allocating object request for the treatment of the allocating object sign for response:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the corresponding object configuration parameter instantiation stateless object according to object identity, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
Therein in embodiment, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time.
Therein in embodiment, described object service condition parameter comprises the number of times and being called the time for the last time of being called of corresponding stateless object.
In embodiment, the total amount that described buffer memory is preserved the stateless object arranges according to default buffer memory total amount parameter therein, and described buffer memory total amount parameter is preserved by default configuration file.
In embodiment, described target cache module 720 specifically comprises therein:
Object identity reading submodule 721, from default configuration file, reading object sign and corresponding object configuration parameter, carry out object-instantiated submodule 722;
Object-instantiated submodule 722, the corresponding object configuration parameter instantiation stateless object according to object identity, and preserve described stateless parameter in buffer memory, and safeguard the corresponding object service condition of stateless object parameter, carry out object detection submodule 723;
Object detection submodule 723, if the total amount of the stateless object of having preserved in buffer memory is less than described buffer memory total amount parameter, and there is the object identity of not instantiation in described configuration file, carry out object identity reading submodule 721, otherwise exit described target cache module 720.
Therein in embodiment, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time, and the stateless object of having preserved in buffer memory adds the above total amount for the treatment of allocating object and is greater than described buffer memory total amount parameter.
The above embodiment has only expressed several embodiment of the present invention, and it describes comparatively concrete and detailed, but can not therefore be interpreted as the restriction to the scope of the claims of the present invention.It should be pointed out that for the person of ordinary skill of the art, without departing from the inventive concept of the premise, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (12)
1. the management method of a JAVA stateless object, is characterized in that, comprising:
Start the IoC container;
The corresponding object configuration parameter instantiation stateless object according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, safeguard the corresponding object service condition of each stateless object parameter;
Response comprises the allocating object request for the treatment of the allocating object sign:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the object configuration parameter corresponding according to object identity is instantiated as the stateless object, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
2. the management method of JAVA stateless object according to claim 1, is characterized in that, the described regular stateless object of rejecting that meets comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time.
3. the management method of JAVA stateless object according to claim 1, is characterized in that, described object service condition parameter comprises the number of times and being called the time for the last time of being called of corresponding stateless object.
4. the management method of JAVA stateless object according to claim 1, is characterized in that, the total amount that described buffer memory is preserved the stateless object arranges according to default buffer memory total amount parameter, and described buffer memory total amount parameter is preserved by default configuration file.
5. the management method of JAVA stateless object according to claim 4, it is characterized in that, object configuration parameter instantiation stateless object corresponding to object identity that described basis is default, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the step of the corresponding object service condition of each stateless object parameter, comprising:
Object identity reads sub-step, and from default configuration file, reading object sign and corresponding object configuration parameter, carry out the object-instantiated sub-step;
The object-instantiated sub-step, the corresponding object configuration parameter instantiation stateless object according to object identity, and preserve described stateless parameter in buffer memory, and safeguard the corresponding object service condition of stateless object parameter, carry out the object detection sub-step;
The object detection sub-step, if the total amount of the stateless object of having preserved in buffer memory is less than described buffer memory total amount parameter, and there is the object identity of not instantiation in described configuration file, carry out object identity and read sub-step, otherwise finish the object configuration parameter instantiation stateless object that the default object identity of described basis is corresponding, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the step of the corresponding object service condition of each stateless object parameter.
6. the management method of JAVA stateless object according to claim 4, it is characterized in that, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time, and the stateless object of having preserved in buffer memory adds the above total amount for the treatment of allocating object and is greater than described buffer memory total amount parameter.
7. the management devices of a JAVA stateless object, is characterized in that, comprising:
Container starts module, for starting the IoC container;
The target cache module, for the object configuration parameter instantiation stateless object corresponding according to default object identity, and preserve described stateless object in the buffer memory by described IoC Container Management, and safeguard the corresponding object service condition of each stateless object parameter;
The object reference module comprises the allocating object request for the treatment of the allocating object sign for response:
Describedly treat that allocating object identifies corresponding stateless object if preserved in described buffer memory, from buffer memory, obtain and describedly treat that allocating object identifies corresponding stateless object as treating allocating object, return to the described allocating object for the treatment of, upgrade the described object service condition parameter for the treatment of that allocating object is corresponding;
Describedly do not treat that allocating object identifies corresponding stateless object if find from buffer memory, according to described, treat that allocating object sign obtains corresponding object configuration parameter, the corresponding object configuration parameter instantiation stateless object according to object identity, to treat that the stateless object of allocating object sign instantiation is as treating allocating object, return to the described allocating object for the treatment of, according to each stateless object of preserving in buffer memory, corresponding object service condition parameter is deleted to meet and is rejected regular stateless object, and preserve the described allocating object for the treatment of in buffer memory, and safeguard and treat the corresponding object service condition of allocating object parameter.
8. the management devices of JAVA stateless object according to claim 7, is characterized in that, the described regular stateless object of rejecting that meets comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time.
9. the management devices of JAVA stateless object according to claim 7, is characterized in that, described object service condition parameter comprises the number of times and being called the time for the last time of being called of corresponding stateless object.
10. the management devices of JAVA stateless object according to claim 7, is characterized in that, the total amount that described buffer memory is preserved the stateless object arranges according to default buffer memory total amount parameter, and described buffer memory total amount parameter is preserved by default configuration file.
11. the management devices of JAVA stateless object according to claim 10, is characterized in that, described target cache module specifically comprises:
The object identity reading submodule, from default configuration file, reading object sign and corresponding object configuration parameter, carry out the object-instantiated submodule;
The object-instantiated submodule, the corresponding object configuration parameter instantiation stateless object according to object identity, and preserve described stateless parameter in buffer memory, and safeguard the corresponding object service condition of stateless object parameter, carry out the object detection submodule;
The object detection submodule, if the total amount of the stateless object of having preserved in buffer memory is less than described buffer memory total amount parameter, and there is the object identity of not instantiation in described configuration file, carry out the object identity reading submodule, otherwise exit described target cache module.
12. the management devices of JAVA stateless object according to claim 10, it is characterized in that, described meeting rejects regular stateless object and comprises: the stateless object of the least number of times that is called in the Preset Time section before the current time, and the stateless object of having preserved in buffer memory adds the above total amount for the treatment of allocating object and is greater than described buffer memory total amount parameter.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2013103789715A CN103425532A (en) | 2013-08-27 | 2013-08-27 | JAVA stateless object management method and device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2013103789715A CN103425532A (en) | 2013-08-27 | 2013-08-27 | JAVA stateless object management method and device |
Publications (1)
Publication Number | Publication Date |
---|---|
CN103425532A true CN103425532A (en) | 2013-12-04 |
Family
ID=49650324
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2013103789715A Pending CN103425532A (en) | 2013-08-27 | 2013-08-27 | JAVA stateless object management method and device |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN103425532A (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104391745A (en) * | 2014-10-13 | 2015-03-04 | 浪潮通用软件有限公司 | Method for managing extensible object life cycle |
CN107145495A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | The method and device of dynamically-adjusting parameter rule |
WO2018072408A1 (en) * | 2016-10-18 | 2018-04-26 | 广州市动景计算机科技有限公司 | Memory analysis method, device, system and computing device |
CN109426601A (en) * | 2017-07-17 | 2019-03-05 | 华为软件技术有限公司 | The method and apparatus that a kind of pair of program is statelessly detected |
CN109683992A (en) * | 2017-10-18 | 2019-04-26 | 北京京东尚科信息技术有限公司 | Method and apparatus for managing object |
CN112801632A (en) * | 2021-02-25 | 2021-05-14 | 北京平恒智能科技有限公司 | Method for realizing customized management of machine vision detection task flow based on control reversal technology |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7581066B2 (en) * | 2005-04-29 | 2009-08-25 | Sap Ag | Cache isolation model |
CN102609255A (en) * | 2012-01-19 | 2012-07-25 | 中国科学院计算机网络信息中心 | Generation method for Spring IOC (Inversion of Control) configuration file |
CN102999319A (en) * | 2011-09-09 | 2013-03-27 | 北京大学 | Method and system for caching function execution result based on aspect-oriented programming (AOP) technology |
-
2013
- 2013-08-27 CN CN2013103789715A patent/CN103425532A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7581066B2 (en) * | 2005-04-29 | 2009-08-25 | Sap Ag | Cache isolation model |
CN102999319A (en) * | 2011-09-09 | 2013-03-27 | 北京大学 | Method and system for caching function execution result based on aspect-oriented programming (AOP) technology |
CN102609255A (en) * | 2012-01-19 | 2012-07-25 | 中国科学院计算机网络信息中心 | Generation method for Spring IOC (Inversion of Control) configuration file |
Non-Patent Citations (2)
Title |
---|
娄锋: "轻量级MTIoC容器的研究与设计", 《中国优秀硕士学位论文全文数据库(信息科技辑)》 * |
王昆: "Spring框架下Web查询性能优化研究", 《中国优秀硕士学位论文全文数据库(信息科技辑)》 * |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104391745A (en) * | 2014-10-13 | 2015-03-04 | 浪潮通用软件有限公司 | Method for managing extensible object life cycle |
CN107145495A (en) * | 2016-03-01 | 2017-09-08 | 阿里巴巴集团控股有限公司 | The method and device of dynamically-adjusting parameter rule |
WO2018072408A1 (en) * | 2016-10-18 | 2018-04-26 | 广州市动景计算机科技有限公司 | Memory analysis method, device, system and computing device |
CN107967205A (en) * | 2016-10-18 | 2018-04-27 | 广州市动景计算机科技有限公司 | A kind of memory analysis method, apparatus, system and computing device |
CN107967205B (en) * | 2016-10-18 | 2020-12-29 | 阿里巴巴(中国)有限公司 | Memory analysis method, device and system and computing equipment |
CN109426601A (en) * | 2017-07-17 | 2019-03-05 | 华为软件技术有限公司 | The method and apparatus that a kind of pair of program is statelessly detected |
CN109426601B (en) * | 2017-07-17 | 2022-05-10 | 华为技术有限公司 | Method and device for carrying out stateless detection on program |
CN109683992A (en) * | 2017-10-18 | 2019-04-26 | 北京京东尚科信息技术有限公司 | Method and apparatus for managing object |
CN109683992B (en) * | 2017-10-18 | 2022-06-07 | 北京京东尚科信息技术有限公司 | Method and apparatus for managing objects |
CN112801632A (en) * | 2021-02-25 | 2021-05-14 | 北京平恒智能科技有限公司 | Method for realizing customized management of machine vision detection task flow based on control reversal technology |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103425532A (en) | JAVA stateless object management method and device | |
US10198351B2 (en) | Optimizing memory usage across multiple applications based on garbage collection activity | |
US9952903B2 (en) | Background task resource control | |
US9189252B2 (en) | Context-based device action prediction | |
US9027027B2 (en) | Thread management based on device power state | |
CN102495857B (en) | Load balancing method for distributed database | |
CN102047218B (en) | Scheduler instances in a process | |
CN104978228B (en) | A kind of dispatching method and device of distributed computing system | |
US8051265B2 (en) | Apparatus for managing memory in real-time embedded system and method of allocating, deallocating and managing memory in real-time embedded system | |
EP2085882A1 (en) | Multiprocessor system, system configuration method in multiprocessor system, and program thereof | |
CN110018899B (en) | Method and device for recycling memory | |
CN104199669A (en) | Method and device for managing application program processes | |
CN107577523B (en) | Task execution method and device | |
US20100115530A1 (en) | Method to track application context and application identification | |
CN107357857A (en) | A kind of method and service node device for updating cache information | |
JPWO2016030973A1 (en) | Multi-tenant resource arbitration method | |
EP3786794A1 (en) | Trusted execution environment scheduling method | |
TW201814529A (en) | Dynamic cache partitioning through hill-climbing | |
CN111064746A (en) | Resource allocation method, device, equipment and storage medium | |
CN102667714A (en) | method and system for enabling access to functionality provided by resources outside of an operating system environment | |
CN104364759A (en) | Method, system and an executable piece of code for controlling the use of hardware resources of a computer system | |
CN106649654A (en) | Data updating method and device | |
WO2022257435A1 (en) | Method and apparatus for processing batch of tasks, computing device, and storage medium | |
CN106650409B (en) | A kind of terminal control method and terminal | |
US20080313652A1 (en) | Notifying user mode scheduler of blocking events |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB03 | Change of inventor or designer information |
Inventor after: Guo Yongqiang Inventor after: Lv Bo Inventor after: Bi Te Inventor before: Guo Yongqiang |
|
CB03 | Change of inventor or designer information | ||
COR | Change of bibliographic data |
Free format text: CORRECT: INVENTOR; FROM: GUO YONGQIANG TO: GUO YONGQIANG LV BO BI TE |
|
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20131204 |
|
RJ01 | Rejection of invention patent application after publication |