Problem with that is that if these objects aren't singletons you're buying a certain amount of heap churn -- and if they are singletons, the advantage
That's why I'm in favor of singletons.
of callback through an event object versus callback through accessors on the cursor itself appears to be negligable-to-absent. (I wrestled with this
I don't agree. I don't consider a clean, layored design to be a "negligable" advantage.
as part of some experiments we're doing in other kinds of XML processing, and came to the conclusion that putting a Node interface on the Cursor/Iterator object itself was at least as clean as having Cursors deliver Nodes.
However, expanding the API is much easier in the node approach as opposed to the cursor one. That's yet another area where the event object approach excels.
SAX's habit of delivering a char{} reference requires it to always create
that array, which may be a nuisance if the source data isn't in that form
That was one thing that I thought about when we were designing XNI. In the end, the simplicity that we gained in the entire implementation won out. But it would have been nice to be able to abstract the character buffer so that transcoding could be deferred, if needed.
-- Andy Clark * [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
