java persistent queue Code
Status: Beta
Brought to you by:
hahn
File | Date | Author | Commit |
---|---|---|---|
src | 2009-03-13 | hahn | [r1] initial checkin of sources |
test | 2009-03-13 | hahn | [r1] initial checkin of sources |
LICENSE.txt | 2009-03-13 | hahn | [r1] initial checkin of sources |
README.txt | 2009-03-13 | hahn | [r1] initial checkin of sources |
build.xml | 2009-03-13 | hahn | [r1] initial checkin of sources |
manifest.mf | 2009-03-13 | hahn | [r1] initial checkin of sources |
project.properties | 2009-03-13 | hahn | [r1] initial checkin of sources |
A lot of projects use java.util.queue because they have no needs for huge JMS implementation. This projects will come in trouble if they get the additional requirements: - to store the queue data persistently, so they can be reused after shutdown or crash - to store huge amount of entries in the queue (java.util.queue stores in memory) This simple implementation stores all queue data on hard drive split in smaller files and provides most methods of interface java.util.queue. There are some restriction in provied Collection and Iteration functionalities of java.util.queue. There are other small queue implementations, in difference to them this implementation: - don't uses (small) RDBM (which makes most solutions slow) - uses the standardized interface java.util.queue - don't hold all queue entries as copy in memory For hints, questions and bug reports please use Sourceforge portal functions or feel free to contact me at mario.hahnemann@freenet.de. This implementation is under GPL. See copy of GPL included in this distribution for details.