axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James M Snell" <jasn...@us.ibm.com>
Subject Re: Parsing stuff
Date Thu, 19 Apr 2001 00:14:42 GMT
Very cool... can't wait to see it.  Do you have any preliminary 
observations on how much of a performance gain there is?

- James Snell
     Software Engineer, Emerging Technologies, IBM
     jasnell@us.ibm.com (online)
     jsnell@lemoorenet.com (offline)

Please respond to axis-dev@xml.apache.org 
To:     "'axis-dev@xml.apache.org'" <axis-dev@xml.apache.org>
cc: 
Subject:        Parsing stuff




I've got a version of the multi-thread SAX parse working, though it needs 
a
bit of cleanup.  It's mostly a proof-of-concept.

I'm going to see if I can make some improvements, clean it up a bit, and
post it to the list tomorrow for review.

Basically, it does exactly what we talked about.  When you create a 
Message
around an InputSource, it spawns a thread which parses the <envelope>
element, makes sure it looks OK, and then suspends.  When anyone asks for
something from the Message (i.e. getHeaderByName(QName)), the parsing 
thread
wakes up and runs until it finds the desired thing or runs out of XML
(initially this just means getting to the end of the headers).  As it 
goes,
it creates SOAPHeader objects, which contain records of the SAX events
inside them, suitable for replaying to any ContentHandler.  Meanwhile the
other thread (the one that made the getHeaderByName() call) blocks until 
the
parse is complete.

Glen Daniels
Macromedia
Engineering Manager
http://www.macromedia.com/
                                Building cool stuff for web developers




Mime
View raw message