Don Seiler wrote:
Yeah this sounds pretty much like what I tried to describe in my other
email that you may receive soon. I'm still unclear on whether or not we
need to make use of DOM here.
If i get the SAX-based implementation of the consumer and the rest of
XML work and documentation done, adding a DOM based consumer is trivial
and would appeal to many users and their use cases (random access is
just appropriate some times).
Is emitting the signal with an array of
Strings a poor idea?
Although it could slow down performance, having something similar with
the Attributes interface of SAX could prove more flexible in the future
and able to carry meta data as well (type information etc). My
objectives are batch processing and periodical updates so others may
dissagree on this.
See you on csv4j,
Manos
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
