axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <gdani...@macromedia.com>
Subject Re: Threading
Date Mon, 30 Apr 2001 13:25:34 GMT
It parses them into a SOAPEnvelope, with (by default) an RPC-style body.

We don't really want to be doing this, for a couple of reasons:

* It causes the entire message to be read into memory.

* We may not be able to determine the desired message format (RPC/Messaging,
plus available type mappings) until we've run through the header handlers
and parse the body to do a lookup/dispatch

The plan, I think, is to move to pull-style incremental parsing, but that's
a next step after we integrate Xerces-2, or XPP....

--G

----- Original Message -----
From: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
To: <axis-dev@xml.apache.org>
Sent: Monday, April 30, 2001 9:03 AM
Subject: Re: Threading


> What does it do with the events?
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Glen Daniels" <gdaniels@macromedia.com>
> To: <axis-dev@xml.apache.org>
> Sent: Monday, April 30, 2001 1:39 AM
> Subject: Threading
>
>
> > I just added a new SOAPSAXHandler child called SAXAdapter, which simply
> > parses the entire message when parse() is called, with no threads.  To
try
> > it out, just replace the "ThreadedSAXAdapter" in Message.java with
> > "SAXAdapter".
> >
> > I didn't do any serious testing, but it looks like the timings improved
> from
> > ~55msg/sec with the ThreadedSAXAdapter to ~70msg/sec with the
non-threaded
> > version.  More tomorrow...
> >
> > --G
> >
> >
>


Mime
View raw message