Sure -- but with each slurp of 32Kb, it can be doing thousands of
syntax callbacks. That easily adds up to seconds of overhead, even
assuming an idle network (no contention). A few years ago I used
200 calls per second as a standard OO RPC speed estimate; it can be
faster, but it can be slower too. And "faster" is not an order of
magnitude faster.
Those callbacks were the worrisome part of your scenario ... :-)
> By the way, Java is simply the initial implementation for SAX, but it
> is not intended to be the only one.
I understand this. But since the master spec isn't in something like
IDL, then you're already committing to language-specific translations
and customizations ... how do you decide which things should be custom,
which shouldn't be? You're not making the tradeoffs I'm used to seeing
when people design systems to use in multiple languages.
- Dave