Hi all, I have added an db4o implementation for storage. The unit tests take aaaaaagggggggeeeessssss to run because what we are doing is the equivalent of starting and initialising a database, running it and then stopping and deleting the database - for each test. So it takes a while. I had an implementation that opened and closed the db for every request for storage (and so equivalent of stopping and starting a database for every query!) but found a much better way that is also much quicker :-). I have left a very ugly hack at the moment by which you must put a full path in the dbname field of the manager for it to work (it ignores the other fields). I would much appreciate your input as to whether I should put in another tab for db4o, or whether I should implement a proper server (it can listen on an arbitrary port and run like a "proper db"), or... There are lots of possibilities, and lots of cool things to do in this project! Cheers Anton
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
