[jdom-interest] Re: progressive parsing/minimizing memory foo tprint

[Scott Smith]

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).

Scott

> -----Original Message-----
> From: Cem Karan [mailto:Cem.Karan at usa.alcatel.com]
> Sent: Wednesday, April 11, 2001 8:38 AM
> To: Joseph Bowbeer
> Cc: jdom-interest at jdom.org
> Subject: [jdom-interest] Re: progressive parsing/minimizing memory
> footprint
> 
....