On Tue, Sep 10, 2002 at 04:44:57PM -0700, Ian Clarke wrote:
> On Wed, Sep 11, 2002 at 12:37:58AM +0100, Matthew Toseland wrote:
> > 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 ne
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
On Wed, Sep 11, 2002 at 12:37:58AM +0100, Matthew Toseland wrote:
> 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 mor
On Tue, Sep 10, 2002 at 04:44:57PM -0700, Ian Clarke wrote:
> On Wed, Sep 11, 2002 at 12:37:58AM +0100, Matthew Toseland wrote:
> > 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 n
On Wed, Sep 11, 2002 at 12:37:58AM +0100, Matthew Toseland wrote:
> 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 mo
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 mappin
