It may make sense to implement several different types of store. a) Native filesystem, with one file per key, and the filename derived from the keyname (may need to escape some chars). Partially implemented already, needs more implementation as well as debugging b) Native filesystem, with a mapping from filename to keyname, and a pool of truncated files (hack to support broken windoze JVMs). Would be a descendant of the class implementing a). c) Everything in a single file, the current datastore that we all know and hate. Implemented fully but has the DSB.
What are the relative urgencies of these options? Should I tackle a) and b) before debugging c) ? If a) and b) are implemented, is c) even necessary? -- Matthew Toseland mtoseland at blueyonder.co.uk amphibian at sourceforge.net Freenet/Coldstore open source hacker. Looking for $coding (I'm cheap) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020911/3c21044f/attachment.pgp>
