For my use-case, the XML is not large at all (~20k). However, the user
experience of having something displayed immediately, and the remaining
content displaying as it loads, is really noticeable. Even if the difference
is sub-second. It's small things that make the application feel faster.
I'd be interested to know what your use case is that requires a SAX
parser. How large is your XML? Did you run into a memory or performance
problem with AS3's E4X capabilities?
- Gordon
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of
Just last week, I had an unsuccessful look around for an AS3 SAX parser. I
thought about making one myself, but couldn't justify the time to fit inside
the project schedule.
Peter
On 5/29/07, Claus Wahlers [EMAIL PROTECTED] wrote:
Paul DeCoursey wrote:
Nobody on this high-volume list
Paul DeCoursey wrote:
Nobody on this high-volume list wants/needs a SAX parser?
Thats just crazy. I'm going back to .NET ;)
Actually, this is something that I have been interested in. I did see
someone had one written for AS2, I don't recall the link. The code
did not translate well to
4 matches
Mail list logo
