CN111367682B - Method, system and device for controlling resource operation lock and readable storage medium - Google Patents
Method, system and device for controlling resource operation lock and readable storage medium Download PDFInfo
- Publication number
- CN111367682B CN111367682B CN202010153470.7A CN202010153470A CN111367682B CN 111367682 B CN111367682 B CN 111367682B CN 202010153470 A CN202010153470 A CN 202010153470A CN 111367682 B CN111367682 B CN 111367682B
- Authority
- CN
- China
- Prior art keywords
- lock
- instance
- locking
- target
- resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000007717 exclusion Effects 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims abstract description 24
- 238000004590 computer program Methods 0.000 claims description 11
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
Images
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/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
- G06F9/526—Mutual exclusion algorithms
Abstract
The application discloses a method, a system and a device for controlling a resource operation lock and a readable storage medium, wherein the method comprises the following steps: defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock; creating a lock instance from the lock structure; acquiring a concurrent exclusion rule of the lock structure; acquiring a target lock instance from all the lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the verification condition comprises the concurrency rejection rule and the locking record; if the availability passes the availability check, locking the target lock instance and recording a locking record; releasing the target lock instance that has been locked and updating the locking record. The application provides a flexibly configured locking mechanism, which can be used for carrying out combined locking on operation and resources to achieve concurrency control of the resources and the operation, and meanwhile, a concurrency rejection rule is set to prevent the problem of disorder caused by concurrent operation of the resources, so that flexible configuration of complex scenes can be realized.
Description
Technical Field
The present invention relates to the field of computer software, and in particular, to a method, a system, an apparatus, and a readable storage medium for controlling a resource operation lock.
Background
In the current software development process, resources are managed and operated more frequently, so that concurrency problems are caused, and in many projects or scenes, concurrency needs to be controlled and managed, mainly exclusive or allowed.
However, in the prior art, only the implementation and application of a basic lock are performed, a code is usually used as a public resource, and lock application is required when executing the part of the code, which is equivalent to that all resources need to apply for the same lock, and thus, the requirements of more flexible and complex scenes are not met, and exclusion and sharing rules among different methods cannot be set.
Therefore, how to provide a solution to the above technical problems is a problem to be solved by those skilled in the art.
Disclosure of Invention
In view of this, the present invention provides a method, a system, a device and a readable storage medium for controlling a resource operation lock, so as to achieve flexible configuration of specific service modules to meet the requirements of complex scenarios. The specific scheme is as follows:
a method for controlling a resource operation lock, comprising:
defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
creating a lock instance from the lock structure;
acquiring a concurrent exclusion rule of the lock structure;
acquiring a target lock instance from all the lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the verification condition comprises the concurrency rejection rule and a locking record;
if the availability check is passed, locking the target lock instance and recording the locking record;
releasing the target lock instance that has been locked and updating the locking record.
Preferably, after the creating the lock instance according to the lock structure, the method further includes:
caching the lock instance in a lock cache pool.
Preferably, the process of acquiring the target lock instance from all the lock instances specifically includes:
judging whether the target lock instance exists in all the lock instances of the lock cache pool or not;
if yes, directly obtaining the target lock instance from the lock cache pool;
and if not, newly building the target lock instance, placing the target lock instance into the lock cache pool, and then acquiring the target lock instance.
Preferably, the process of locking the target lock instance includes:
and carrying out operation locking, resource locking or resource operation locking on the target lock instance.
Preferably, the process of locking the target lock instance and recording the locking record specifically includes:
and locking the target lock instance and recording a locking record so as to add the state of the target lock instance into the next locking check condition.
Preferably, the process of checking availability of the target lock instance according to the checking condition specifically includes:
judging whether the target lock instance simultaneously meets the following conditions:
the target lock instance complies with the concurrency rejection rules;
the target lock instance does not exist in the locking record, or the target lock instance in the locking record is in a released state;
if so, determining that the target lock instance passes the availability check.
Correspondingly, the invention also discloses a control system of the resource operation lock, which comprises the following steps:
an internal lock module for defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
a lock factory for creating lock instances from the lock structure;
a lock rule manager for setting a concurrency rejection rule of the lock structure;
the lock manager is used for acquiring target lock instances from all the lock instances, performing availability check on the target lock instances according to check conditions, locking the target lock instances and recording locking records if the availability check is passed, and releasing the locked target lock instances and updating the locking records; the verification condition includes the concurrency rejection rule and the locking record.
Preferably, the control system further comprises a lock cache pool for caching all the embodiments created by the lock factory.
Correspondingly, the invention also discloses a control device of the resource operation lock, which comprises the following components:
a memory for storing a computer program;
a processor for implementing the steps of the method of controlling a resource handling lock as claimed in any one of the preceding claims when executing said computer program.
Correspondingly, the invention also discloses a readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method for controlling a resource operation lock as described in any one of the above.
The application discloses a control method of a resource operation lock, which comprises the following steps: defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock; creating a lock instance from the lock structure; acquiring a concurrency rejection rule of the lock structure; acquiring a target lock instance from all the lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the verification condition comprises the concurrency rejection rule and the locking record; if the availability passes the verification, locking the target lock instance and recording a locking record; releasing the target lock instance that has been locked and updating the locking record. The application provides a flexibly configured locking mechanism, which can be used for carrying out combined locking on operation and resources to achieve concurrency control of the resources and the operation, and meanwhile, a concurrency rejection rule is set to prevent the problem of disorder caused by concurrent operation of the resources, so that flexible configuration of complex scenes can be realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flowchart illustrating steps of a method for controlling a resource operation lock according to an embodiment of the present invention;
FIG. 2 is a dependency diagram of a control system for a resource operation lock according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
At present, the prior art only locks the operation, does not meet the requirements of more flexible and complex scenes, and cannot set exclusion and sharing rules among different methods. The application provides a flexibly configured locking mechanism, so that concurrent control of resources and operations is achieved, and flexible configuration of complex scenes can be achieved.
The embodiment of the invention discloses a method for controlling a resource operation lock, which is shown in figure 1 and comprises the following steps:
s1: defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
s2: creating a lock instance from the lock structure;
further, after step S2, the method may further include:
lock instances are cached in a lock cache pool.
It will be appreciated that caching the created lock instance provides a basis for achieving reusability of the lock instance and uniqueness of the same lock instance.
S3: acquiring a concurrent exclusion rule of a lock structure;
the concurrency rejection rule is usually set according to an instruction input by a programmer, and the instruction can be in the form of:
LockRuleManager.addConcurrentRules(operation[]),
LockRuleManager.addExclusiveRules(operation[]).
thereby allowing exclusive operation or allowing concurrent operation through the instruction configuration. The concurrency rejection rules are usually set and rarely changed, the instruction is usually input in the initialization stage of the whole control system, and in addition, the concurrency rejection rules can be set by using the instruction only in special cases, such as the case of a lock instance which is not locked currently.
S4: acquiring a target lock instance from all lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the checking condition comprises a concurrency rejection rule and a locking record;
in step S4, generally, the determination and the acquisition of the target lock instance are performed according to the ID information, and in order to ensure the uniqueness of the lock instance, the target lock instance is preferentially searched from the cached lock instance, and if the target lock instance exists in the lock cache pool, the target lock instance is directly acquired, and if the target lock instance does not exist in the lock cache pool, a new target lock instance needs to be created first to ensure the uniqueness of the same lock instance, so the process of acquiring the target lock instance in all the lock instances specifically includes:
judging whether all lock instances in the lock cache pool have target lock instances or not;
if yes, directly obtaining a target lock instance from a lock cache pool;
if not, the target lock instance is newly built and placed in the lock cache pool, and then the target lock instance is obtained.
Further, the process of checking availability of the target lock instance according to the checking condition specifically includes:
judging whether the target lock instance simultaneously meets the following conditions:
the target lock instance complies with concurrency rejection rules;
the target lock instance does not exist in the locking record, or the target lock instance in the locking record is in a released state;
if so, the target lock instance is determined to pass the availability check.
It can be understood that the basis of the availability check in this embodiment is three exclusive requirements in the control system: resource lock exclusion, namely locking a certain resource to achieve the exclusion effect, and the same resource cannot be locked twice; operation lock exclusion, i.e., all resources of the same operation are excluded; resource operation lock exclusion, that is, ensuring different operations of a certain resource to be excluded or concurrent according to a concurrency exclusion rule set by an instruction, such as A and B exclusion, B and C exclusion, but A and C can be concurrent.
S5: if the availability passes the verification, locking the target lock instance and recording a locking record;
it will be appreciated that locking cannot be performed if the availability check is not passed.
Specifically, the step S5 is a process of locking the target lock instance, and includes:
and carrying out operation locking, resource locking or resource operation locking on the target lock instance.
It can be understood that the lock structure includes an operation lock, a resource lock, and a resource operation lock, and correspondingly, the action of locking includes an operation lock, a resource lock, and a resource operation lock, where the operation lock is to lock a certain operation of all resources, the resource lock is to lock all operations of a certain resource, and the resource operation lock is to lock a certain operation of a certain resource. The code form can be the following forms in turn:
LockManager.lock(resource id),
LockManager.lock(operation),
LockManager.lock(resource id,operation).
similarly, the release of the locked target lock instance may be in the following form:
LockManager.unlock(resource id),
LockManager.unlock(operation),
LockManager.unlock(resource id,operation).
further, the process of locking the target lock instance and recording the locking record specifically includes:
and locking the target lock instance and recording a locking record so as to add the state of the target lock instance to the next locking check condition.
S6: the locked target lock instance is released and the locking record is updated.
The embodiment of the application discloses a method for controlling a resource operation lock, which comprises the following steps: defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock; creating a lock instance from the lock structure; acquiring a concurrent exclusion rule of a lock structure; acquiring a target lock instance from all lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the checking condition comprises a concurrency rejection rule and a locking record; if the availability passes the verification, locking the target lock instance and recording a locking record; the locked target lock instance is released and the locking record is updated. The embodiment of the application provides a flexibly configured locking mechanism, which can be used for performing combined locking on operation and resources to achieve concurrent control of the resources and the operation, and meanwhile, a concurrent exclusion rule is set to prevent the problem of disorder caused by concurrent operation of the resources, so that flexible configuration of complex scenes can be realized.
The embodiment of the invention discloses a control system of a resource operation lock, which is shown in figure 1 and comprises the following components:
an internal lock module 1 for defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
a lock factory 2 for creating lock instances according to a lock structure;
a lock rule manager 3 for setting a concurrency rejection rule of the lock structure;
the lock manager 4 is used for acquiring the target lock instance from all the lock instances and verifying the availability of the target lock instance according to the verification condition; if the availability passes the verification, locking the target lock instance and recording a locking record; the lock management system is also used for releasing the locked target lock instance and updating the locking record; the check condition includes a concurrency rejection rule and a locking record.
Wherein an instruction may be input to the lock rule manager 3 to set the concurrency rejection rule, the instruction may be in the form of:
LockRuleManager.addConcurrentRules(operation[]),
LockRuleManager.addExclusiveRules(operation[]).
thereby allowing exclusive operation or allowing concurrent operation through the instruction configuration. Normally, the concurrency rejection rules in the lock rule manager 3 are changed little after setting, the instruction is usually input in the initialization stage of the whole control system, and in addition, the concurrency rejection rules can be set by using the instruction only in special cases, such as the case that the current locked lock instance is empty.
Further, the control system comprises a lock cache pool 5 for caching all lock instances created by the lock factory 2.
It will be appreciated that the lock cache pool 5 is used to cache lock instances, ensuring reusability of lock instances and uniqueness of the same lock instance.
Further, the process of the lock manager 4 acquiring the target lock instance in all the lock instances specifically includes:
judging whether all the lock instances in the lock cache pool 5 have target lock instances;
if yes, directly obtaining a target lock instance from the lock cache pool 5;
if not, a target lock instance is newly built through the lock factory 2 and is placed in the lock cache pool 5, and then the target lock instance is obtained.
It can be understood that, the lock manager 4 must pass through the lock factory 2, and the lock factory 2 determines, according to the information of the target lock instance, whether to newly build the target lock instance or directly obtain the target lock instance from the lock cache pool 5, preferentially obtains the target lock instance from the lock cache pool 5, and if the target lock instance does not exist in the lock cache pool 5, the lock factory 2 newly builds the target lock instance to ensure the uniqueness of the same lock instance.
Further, the process of locking the target lock instance by the lock manager 4 specifically includes:
and carrying out operation locking, resource locking or resource operation locking on the target lock instance.
It can be understood that the lock structure includes an operation lock, a resource lock, and a resource operation lock, and correspondingly, the action of locking by the lock manager includes an operation lock, a resource lock, and a resource operation lock, where the operation lock is to lock a certain operation of all resources, the resource lock is to lock all operations of a certain resource, and the resource operation lock is to lock a certain operation of a certain resource. The code form can be the following forms in turn:
LockManager.lock(resource id),
LockManager.lock(operation),
LockManager.lock(resource id,operation).
similarly, the release of the locked target lock instance may be in the following form:
LockManager.unlock(resource id),
LockManager.unlock(operation),
LockManager.unlock(resource id,operation).
further, the process of the lock manager 4 recording the target lock instance specifically includes:
and recording the target lock instance to add the state of the target lock instance to the next locking check condition.
Further, the process of the lock manager 4 performing availability check on the target lock instance according to the check condition specifically includes:
judging whether the target lock instance simultaneously meets the following conditions:
the target lock instance complies with concurrency rejection rules;
the target lock instance does not exist in the locking record, or the target lock instance in the locking record is in a released state;
if so, the target lock instance is determined to pass the availability check.
It can be understood that the basis of the availability check in the present embodiment is three exclusive requirements in the control system: resource lock exclusion, namely locking a certain resource to achieve the exclusion effect, and the same resource cannot be locked twice; operation lock exclusion, i.e., all resources of the same operation are excluded; resource operation lock exclusion, that is, ensuring different operations of a certain resource to be excluded or concurrent according to a concurrency exclusion rule set by an instruction, such as A and B exclusion, B and C exclusion, but A and C can be concurrent.
It can be understood that, in the present embodiment, each module of the control system appears in the form of a packaged program module, which facilitates global usage. With the difference between the system framework and the used programming language, the form of the control system of the resource operation lock in this embodiment needs to be adaptively adjusted and modified, but the respective role of each module and the processes of three lock structures, concurrent exclusion rules, and availability check in the control system in this embodiment all belong to the protection objects of the solution of this application.
The control system in this embodiment utilizes the lock instance to lock or release the lock externally, and the whole control system is invisible to the outer layer and only has internal control. The system is simple to implement, the implementation model mainly comprises exclusive locks, and part of designs need to support concurrency in a locking scene, so that concurrency control of resources and operation can be achieved, and the problem of disorder caused by concurrency of resources is prevented.
The lock instance provides a flexibly configured locking mechanism, the operation and the resource can be combined and locked, the concurrent control of the resource and the operation is achieved, the concurrent exclusion rule is set, the disorder problem caused by the concurrent operation of the resource is prevented, and therefore the flexible configuration of complex scenes can be achieved.
Correspondingly, the embodiment of the invention also discloses a control device of the resource operation lock, which comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the method for controlling a resource operation lock according to any one of the above embodiments when executing the computer program.
The specific content of the control method related to the resource operation lock in this embodiment may refer to the description of the above embodiments, and is not described herein again.
The control device of this embodiment has the same beneficial effects as the control method of the resource operation lock, and is not described herein again.
Correspondingly, the invention also discloses a readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method for controlling a resource operation lock according to any one of the above embodiments.
The specific content of the control method related to the resource operation lock in this embodiment may refer to the description of the above embodiments, and is not described herein again.
The readable storage medium of this embodiment has the same beneficial effects as the control method of the resource operation lock, and is not described herein again.
Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The method, system, apparatus and readable storage medium for controlling a resource operation lock provided by the present invention are described in detail above, and a specific example is applied herein to illustrate the principle and implementation of the present invention, and the description of the above embodiment is only used to help understand the method and core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, the specific embodiments and the application range may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (8)
1. A method for controlling a resource operation lock, comprising:
defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
creating a lock instance from the lock structure;
acquiring a concurrent exclusion rule of the lock structure;
acquiring a target lock instance from all the lock instances, and carrying out availability verification on the target lock instance according to verification conditions; the verification condition comprises the concurrency rejection rule and a locking record;
if the availability check is passed, locking the target lock instance and recording the locking record;
releasing the locked target lock instance and updating the locking record;
the process of locking the target lock instance comprises:
performing operation locking, resource locking or resource operation locking on the target lock instance;
the process of locking the target lock instance and recording the locking record specifically includes:
and locking the target lock instance and recording the locking record so as to add the state of the target lock instance into the next locking check condition.
2. The control method according to claim 1, wherein after creating the lock instance according to the lock structure, further comprising:
caching the lock instance in a lock cache pool.
3. The control method according to claim 2, wherein the process of acquiring the target lock instance among all the lock instances specifically comprises:
judging whether the target lock instance exists in all the lock instances of the lock cache pool or not;
if yes, directly obtaining the target lock instance from the lock cache pool;
and if not, newly building the target lock instance, placing the target lock instance into the lock cache pool, and then acquiring the target lock instance.
4. The control method according to any one of claims 1 to 3, wherein the process of checking availability of the target lock instance according to the checking condition specifically includes:
judging whether the target lock instance simultaneously meets the following conditions:
the target lock instance complies with the concurrency rejection rules;
the target lock instance does not exist in the locking record, or the target lock instance in the locking record is in a released state;
if so, determining that the target lock instance passes the availability check.
5. A control system for a resource operated lock, comprising:
an internal lock module for defining a lock structure; the lock structure comprises an operation lock, a resource lock and a resource operation lock;
a lock factory for creating lock instances from the lock structure;
a lock rule manager for setting a concurrency rejection rule of the lock structure;
the lock manager is used for acquiring target lock instances from all the lock instances, verifying the availability of the target lock instances according to verification conditions, locking the target lock instances and recording locking records if the availability is verified, and also used for releasing the locked target lock instances and updating the locking records; the verification condition comprises the concurrency rejection rule and the locking record;
the process of locking the target lock instance by the lock manager includes:
performing operation locking, resource locking or resource operation locking on the target lock instance;
the process of locking the target lock instance and recording the locking record by the lock manager specifically includes:
and locking the target lock instance and recording the locking record so as to add the state of the target lock instance into the next locking check condition.
6. The control system of claim 5, further comprising a lock cache pool for caching all of the lock instances created by the lock factory.
7. A control apparatus for a resource operated lock, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the method of controlling a resource handling lock according to any one of claims 1 to 4 when executing said computer program.
8. A readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of a method for controlling a resource handling lock according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010153470.7A CN111367682B (en) | 2020-03-06 | 2020-03-06 | Method, system and device for controlling resource operation lock and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010153470.7A CN111367682B (en) | 2020-03-06 | 2020-03-06 | Method, system and device for controlling resource operation lock and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111367682A CN111367682A (en) | 2020-07-03 |
| CN111367682B true CN111367682B (en) | 2022-07-08 |
Family
ID=71206595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010153470.7A Active CN111367682B (en) | 2020-03-06 | 2020-03-06 | Method, system and device for controlling resource operation lock and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111367682B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114679465A (en) * | 2022-03-28 | 2022-06-28 | 北京火山引擎科技有限公司 | Resource operation method and device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160048673A1 (en) * | 2013-03-22 | 2016-02-18 | Utc Fire And Security Americas Corporation, Inc. | Secure electronic lock |
| CN105573823A (en) * | 2014-10-09 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Resource locking method and device |
| CN110554914A (en) * | 2019-07-15 | 2019-12-10 | 厦门网宿有限公司 | Resource lock management method, device, server and storage medium |
-
2020
- 2020-03-06 CN CN202010153470.7A patent/CN111367682B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160048673A1 (en) * | 2013-03-22 | 2016-02-18 | Utc Fire And Security Americas Corporation, Inc. | Secure electronic lock |
| CN105573823A (en) * | 2014-10-09 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Resource locking method and device |
| CN110554914A (en) * | 2019-07-15 | 2019-12-10 | 厦门网宿有限公司 | Resource lock management method, device, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111367682A (en) | 2020-07-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8112745B2 (en) | Apparatus and method for capabilities verification and restriction of managed applications in an execution environment | |
| US8448175B2 (en) | Deadlock detection in a parallel program | |
| GB2513528A (en) | Method and system for backup management of software environments in a distributed network environment | |
| US20200026859A1 (en) | Methods and systems for system call reduction | |
| US11720607B2 (en) | System for lightweight objects | |
| CN111367682B (en) | Method, system and device for controlling resource operation lock and readable storage medium | |
| CN114281653B (en) | Application program monitoring method and device and computing equipment | |
| US8458151B2 (en) | Network device and method for updating data of the network device | |
| CN111666088A (en) | Pod replacement method and device, electronic equipment and computer-readable storage medium | |
| WO2019212727A1 (en) | Storage reserve in a file system | |
| EP0889396B1 (en) | Thread synchronisation via selective object locking | |
| US7418713B2 (en) | Component processing system and component processing method | |
| Aghazadeh et al. | Upper bounds for boundless tagging with bounded objects | |
| CN112487010B (en) | Block chain user data table updating method, equipment and storage medium | |
| US20050198005A1 (en) | Systems and methods for controlling access to an object | |
| CN109033802B (en) | Method and device for achieving system permission acquisition of unauthorized android application | |
| CN111488142A (en) | Embedded aeronautical communication middleware supporting multiple operating system platforms and application thereof | |
| JP4937387B2 (en) | Automatic rewriting program and automatic rewriting device | |
| US20230048971A1 (en) | System and method for utilizing checklists for lifecycle management in a case management system | |
| US9477696B2 (en) | Serializing resource utilization using hardware built-in functions | |
| CN114416283A (en) | Container resource control method and device, electronic equipment and storage medium | |
| JPH09269912A (en) | Information processing method and information processor | |
| CN116302320A (en) | Method and system for blocking illegal image deployment of K8s platform | |
| CN117493874A (en) | Method for determining label calculation task, processor and storage medium | |
| CN116820536A (en) | Unified management method for multiple thread pools |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |