Tree structures like the DOM arent memory friendly by default. You get great
functionality, and flexibility but at the expense of runtime memory usage. I
havent looked into Xalan that much so I can't make a useful contribution to
that route. But in an environment like the Palm you are definitly going to
run into memory constraints. My Palm III color have 8MB of memory, so after
the Xerces APIs are loaded, you will have a finite amount of space to work
in. What would be interesting is a "rolling DOM", where you have a fixed
buffer size (say 2MB), and the DOM will shift in and out of that buffer
while traversing the tree structures. There is another problem though. Most
palms dont have harddrives that have a stick of memory that acts as both
ROM, and RAM. This makes the buffer pointless unless you where in a
networking environment.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 28, 2001 2:49 PM
To: [EMAIL PROTECTED]
Subject: RE: xerces parser on Palm?
>Maybe the parser, but you can forget about the DOM
I have to register a protest here. Remember, the DOM is _only_ an API and
says nothng about its back-end storage. Compact versions can and do exist;
Xalan is in the process of reviving and extending our DTM model, to take
one (admittedly somewhat subsetted) example.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
