On Wed, Sep 04, 2002 at 11:12:03PM -0700, Tracy R Reed wrote: > Next time my datastore tosses its cookies what should I do? What > information do you need? I'd like to help however possible.
I don't think there is much that can be done by the general public, I suspect that diagnosing the problem would require reproducing it in controlled conditions, and having the understanding of the code to diagnose from there. > Not a bad idea. Did Tavin get hit by a bus or something? Good question. > If someone else is working on a native datastore then I would suggest > letting them do their thing while we figure out what's wrong with the > current datastore. Well, perhaps - I don't know what their ETA is, and we have been burnt before by holding everything up while someone works on completing something without a reasonable committment as to when it will be done, it cost us months of development time. > The question should be this: Is Tavin's design good and > worth salvaging or is it poorly designed and bound to be full of problems > forever? My understanding is that it is good, although it is not clear where the boundaries are between the different components of his implementation (ie. exactly what needs to be replaced to achieve what goals). > Isn't a single file datastore quite hard to debug? I'm always a fan of not > reinventing the wheel so it would seem wise to let native filesystems do > as much as possible. Not if it is built starting with small building-blocks and working up from there, unit testing all the time. Ian. -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ Personal Homepage http://locut.us/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020904/1969883e/attachment.pgp>
