Lists Home |
Date Index |
in a sense, that sounds like an alternative interface to an abstract document
object model to me. what would be the qualitative difference?
Rick Jelliffe wrote:
> I am idly wondering whether unpooled steaming Java APIs of XML documents (e.g. SAX)
> really make as much sense as we might like them to.
> It strikes me that there are two factors that undermine the benefits of streaming processing:
> * XML documents are rarely smaller than memory
> * Java implementations typically only garbage collect when they get "near"
> to filling their heaps.
> These two things conspire to make it that, for the lion's share of documents,
> by the time the SAX stream is finished, all the SAX events will be still
> in memory, though perhaps unreachable. If they are in memory, why not
> make them available?
> Does that sound right to anyone?