From: Adrian S. J. <AS...@pa...> - 2002-01-14 14:04:14
|
> From: Adrian St. John=20 >=20 > > From: J.P. King [mailto:jp...@he...] > >=20 > >=20 > > Having said I could only find one so far, I then find another, which > > is more our cup of tea: > >=20 > > http://sourceforge.net/projects/coldstore/ > >=20 > > I haven't looked at the code itself yet. >=20 > Quote from their website: >=20 > MUDs, MOOsm MUSHes, M*=20 > It's a good way to store those objects. [ColdStore could=20 > almost have been designed to implement a M* :) ] >=20 (Yes, I'm following up to my own post...) Taking a step back, what problem are we trying to solve? If we're looking for a secure way of storing the data, then this isn't it. It is in-process, and therefore prone to the same problems we have already (if we crash unexpectedly the data could be in a bad state). I think that what we're really after is an out-of-process object store that can be connected to by different processes (UglyMUG engine, Web interface, low-level db hacking tool) at the same time, and provide a minimal amount of consistancy (eg no half-written strings, having to use a database snapshot from up to an hour ago). Admittedly in front of that should be a local-process cache that holds some details (the common strings, flags, etc), or possibly the whole object, or even depending on what we're doing, tell the database how much to cache. Adrian. |