The feel of a LispM/List of running machines

[Chris Bitmead uid(x22068)]

>> Many object databases have the concept of a "segment" which is a
>> logical area of the database to allow grouping of related
>> objects. This helps with performance.
>> 
>The way we handle persistence is to allow the creation of .db files called

Who is "We" BTW.

>Anyway, rather than maintaining OODBMS-style "segments" (POET calls
>them "extents"), we just create different .db files. This splits the
>difference between the 1-to-1 and 1-to-all approaches. Seems to work
>pretty well. Usually, we only end up with a a few .db files, with the
>customer's environment and data requirements driving the architecture.

I think we are talking about the same thing. 1 file = 1 lisp
repository.

I do slightly disagree in that we might want to aim for a lot more
that a couple of .db files. I can imagine someone loading LispOS on
top of their Linux system, and then deleting some packages they don't
want hoping to give the space back to UNIX. If there is one .db file
holding everything UNIX won't ever get space back.

>BTW, we don't need no steenkin' ODL (save Lisp itself)!! You create it, you
>store it -- no extra, external, OODBMS-like steps required. 

I agree!