Giuseppe Bilotta wrote: > Tuesday, December 6, 2005 John W. Kennedy wrote: > >> There is /one/ issue that comes up here. /Does/ OOo parse the XML on the >> fly as it is unpacked, or does it produce the (e.g.) 45MB XML files and >> then parse and discard them? Similarly, when saving, are the XML files >> produced and then compressed and discarded, or are they compressed on >> the fly? There is an obvious optimization to be attempted here, if it >> has not been done. > > I would place my bet on the dumb-and-slow > load-the-whole-file-and-then-process-it approach, which is > what makes OOo so unbearably slow. Although I haven't had a > look at the code and thus cannot be sure, I remember a few > comments (triggered by the ZDNet comparison) to this > purpose.
You are lucky that you didn't place the bet. :-) OOo doesn't do that. First it processes each XML stream independently (and other streams only on demand) and second it never loads any whole uncompressed stream into memory but instead has an "unpacking" buffer that on one side is filled by uncompressing (on demand) and on the other side is processed by the XML parser. When the internal pointer in the buffer is moved to the end more data gets uncompressed to the buffer and so on. This works for the xml processing because no seeking back is necessary. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
