yiisoft
Stoppable behavior
Related #87.
The code is simple and anyone can create it inside own project. But maybe need to create abstract class which will include stopping logics, and cache component should be moved into child?
This wont work when your dealing with EA filecache and 2 different services, It requires to that the runner and pusher use the same cache instance.
This wont work when your dealing with EA filecache and 2 different services, It requires to that the runner and pusher use the same cache instance.
could be added as a note to the phpdoc.
I don't like this approach at all.
- There is no guarantee they will actually be stopped (a cache is not persistent reliable storage).
- It uses the cache as some kind of quick storage, that is not what it is for.
- If the cache is not reachable for whatever reason, all workers will stop working.
- Several drivers already implement
remove()(file, db, beanstalk, redis).
The exceptions here are amqp and gearman.
In the cases where you use amqp / gearman and you have multiple workers, you will need a shared cache.
If you are on the same host then you could use files storage, but in that case you could just as well use the file queue driver since you're depending on the file system anyway.
If you're on different hosts you'll probably end up using a cache driver like redis or memcache; in which case you could just as well use redis for your queue in the first place.
As OP mentioned, implementing it in your own project is simple. Since this (in my opinion) is hardly ever the best, or even a good, solution I think adding this behavior will result in worse decisions by developers.
