[jdom-interest] JDOM & Virtual memory file

[Joseph Bowbeer]

I mentioned in my response to "progressive" that Java Data Objects (JDO)
aims to accomplish this in a generic fashion, for any class.

 Java Data Objects (JDO)
 http://java.sun.com/aboutJava/communityprocess/review/jsr012/

Presumably, the JDO enhancer will be able to create a persistence capable
version of JDOM's Document class automatically.   Another option would be
for Document (or PersistableDocument?) to implement Persistable explicitly.

----- original message -----
From: Scott Smith ssmith at summitlogic.com
Date: Wed, 11 Apr 2001 15:38:38 -0700

Has the topic of a JDOM using virtual memory come up before?  I don't mean
using the OS's virtual memory. I mean explicitly have the JDOM Document
manage it's own virtual memory file.  It may sound slightly crazy, but it
seems that if a JDOM doc managed it's own VM file directly, it would be much
more efficient than the generic VMM offered by the OS.  For instance, each
element could be stored contiguously on disk. A ElementBlockSize setting
could determine how large an element could be before it is stored in a
separate block (linked to its parent).

I posted this earlier as a response to the "Re: progressive
parsing/minimizing memory" subject, and it didn't get any response.

Scott