Hi! Over the last few months we worked on ZendQueue<https://github.com/ripaclub/ZendQueue> component refactoring.
Inspired by the original RFC ( http://webcache.googleusercontent.com/search?q=cache:yoyvW8ZtPOoJ:framework.zend.com/wiki/display/ZFDEV2/RFC%2B-%2BZend%2BQueue%2BRefactoring+&cd=1&hl=it&ct=clnk&gl=it <http://webcache.googleusercontent.com/search?q=cache:yoyvW8ZtPOoJ:framework.zend.com/wiki/display/ZFDEV2/RFC%2B-%2BZend%2BQueue%2BRefactoring+&cd=1&hl=it&ct=clnk&gl=it>) and some new ideas about component usages, we made a not backward compatible refactor of https://github.com/zendframework/ZendQueue (never officially release and in a bad state yet). Reconsidering adapters choice we removed some old adapters (like Memcacheq and PlatformJobQueue, also we introduced two MongoDB-based adapters, with particular regard to Mongo's capped collection approach for creating a simple message queue (http://shtylman.com/post/the-tail-of-mongodb/ ). He following adapters are implemented and tested: - ArrayAdapter (mock/testing) - Db (with table and row gateways) - MongoCappedCollection (supports just one queue per collection) - MongoCollection (supports just one queue per collection) - Null (used to disable a queue and testing) The following new features are introduced and tested: - Send / Receive parameters - Adapter Capabilities Interfaces - Real await (MongoCappedCollection) and emulated await - QueueOptions, factories and service factories etc etc.. We'd like your opinion, also we'd like to know if our implementation is acceptable for the official repository<https://github.com/zendframework/ZendQueue> otherwise we've to found a way to make it a stable repository (because we're using already it in various projects, maybe using another namespace instead of ZendQueue). Thanks by https://github.com/orgs/ripaclub/members -- Gianluca Arbezzano www.gianarb.it
