> > Okay, this is just an idea ... Why not support a real database then to store > the data (read the first * below before you react)? Precisely.
> > * JDBC api is simple and I don't think it'd be hard to add as an /option/ to > the node. > * The database would still need to be "maintained" (as far as size, etc) as > it does now. > * Lets you split up the node and the datastore onto different machines, if > traffic becomes that much of a problem, or you want to use another machine's > disk. > * Have to maintain the database server, but as only advanced users would use > it, that shouldn't be too much of a problem. Seriously. If you're running a monster node like that, you should be using proven technologies meant to handle this sort of thing, like relational databases. -------------- 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/20000803/0c51027b/attachment.pgp>
