[
Lists Home |
Date Index |
Thread Index
]
Roger Costello wrote:
> > Why not just stream the XML?
>
> What's the difference between streaming SAX events versus "streaming
> the XML"? /Roger
I'm not sure what context you're doing this in, but it seems like
granularity and transparency are the two big issues. Making every SAX
event into a tiny binary transmission (over RMI, CORBA, etc.) has some
problems.
Sending individual SAX events seems to require a lot of overhead in
sending small chunks of varied information. Sending larger pieces
(something MOE, which I mentioned yesterday, is designed to support)
seems to make more sense in most network-transmission scenarios.
On the transparency, sending XML, even XML fragments, seems easier to
deal with than most message formats, though you could preserve the
transparency by using an XML-based message format. Even XML-RPC for
SAX2 seems like a lot, though.
Or maybe you were planning on transmitting "SAX events" using pieces of
XML? The start tag for startElement() maybe? There are lots of
different possibilities.
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com
|
