Download the PHP package lysice/hyperf-redis-lock without Composer
On this page you can find all versions of the php package lysice/hyperf-redis-lock. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package hyperf-redis-lock
hyperf-redis-lock
English | 中文
an easy redis-based distributed-lock implementation for hyperf 2.*。 This extension features distributed-lock includes block and unblock distributed-lock.
Principle
The command in Redis is atomic.so we use set to make sure that your application executes sequentially.
The Redis version before 2.8 does't support the option ex in set command. so we just use setnx+expire instead.>> Version 1.
The Redis version after 2.8 supports the option ex in set command. so we use set nx ex>> Version 2.
so version 2. supports the version of redis after 2.8. version 1. supports all the versions of redis.
Redis version
redis-server --version
Install
Run composer require lysice/hyperf-redis-lock
Usage
init the redis object
-
non-block lock we try to acquire the lock then return the result directly.If acquire the lock, execute the Closure and return the Closure's result. or return false;
- blocking lock
we try acquire the lock first.
1.if failed we try to acquire the lock every 250 ms util timeout(the time we waiting for is bigger than the expire time you set in your application)
2.if success then execute the closure and return the result of closure.
Tips: if timeout occurs in the process of application you need to catch the exceptionLockTimeoutExceptionto handle this situation. for example:
Finally
Contributing
Feel free to create a fork and submit a pull request if you would like to contribute.
Bug reports
Raise an issue on GitHub if you notice something broken.
