[Home] [By Thread] [By Date] [Recent Entries]


>     I've gotten pretty good at assembling a SAX engine quickly by
>     composing one using resuable strategies.

Alan,

you didn't answer my question. Besides the personal
interest and fun, where there any technical reasons why
Xquery/XSLT wouldn't have been the right choice ?

Instead of writing Java over SAX, isn't it more convenient
to write:

for $x in //foobar
where some:predicate($x)
return my:function($x)

  and leave the smart streaming strategies to implementors
to figure out ?

Did you try XQuery/XSLT and fail ? If yes, where did they
fell short ?

Best regards
Dana





Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member