Return-Path: 
 <axis-dev-return-791-apmail-xml-axis-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org
Received: (qmail 18371 invoked by uid 500); 19 Apr 2001 15:52:05 -0000
Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
list-help: <mailto:axis-dev-help@xml.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@xml.apache.org>
list-post: <mailto:axis-dev@xml.apache.org>
Delivered-To: mailing list axis-dev@xml.apache.org
Received: (qmail 18130 invoked from network); 19 Apr 2001 15:51:46 -0000
Received: from e32.co.us.ibm.com (HELO e32.bld.us.ibm.com) (32.97.110.130)
  by h31.sny.collab.net with SMTP; 19 Apr 2001 15:51:46 -0000
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com
 [9.99.140.23])
	by e32.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA50838
	for <axis-dev@xml.apache.org>; Thu, 19 Apr 2001 11:52:14 -0400
Received: from f6n96e (d03nm104h.boulder.ibm.com [9.99.140.96])
	by westrelay02.boulder.ibm.com (8.8.8m3/NCO v4.96) with ESMTP id JAA138178
	for <axis-dev@xml.apache.org>; Thu, 19 Apr 2001 09:51:47 -0600
Importance: Normal
To: axis-dev@xml.apache.org
Subject: Re: Parsing stuff
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF2564368D.11619593-ON88256A33.0056FA1B@LocalDomain>
From: "James M Snell" <jasnell@us.ibm.com>
Date: Thu, 19 Apr 2001 08:51:36 -0700
X-MIMETrack: Serialize by Router on D03NM104/03/M/IBM(Release 5.0.6 |December
 14, 2000) at
 04/19/2001 09:51:47 AM,
	Serialize complete at 04/19/2001 09:51:47 AM
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Yup.... shore are.  Which is probably why we don't want to use this 
approach but I think that it is definitely worthwhile to at least explore 
it (at the very least to rule it out as an option).  I believe that xalan 
is trying to move away from this approach. 

- 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>
cc: 
Subject:        Re: Parsing stuff



Aren't there major issues with app servers and thread management? I
thought that part of the server side programming model was that
user application components are not spsed to be creating threads ..
the app server does thread creation and mgmt.

I believe Xalan does something like this with DTM. I wonder how they
addressed this issue.

Sanjiva.

----- Original Message -----
From: "Glen Daniels" <gdaniels@macromedia.com>
To: <axis-dev@xml.apache.org>
Sent: Wednesday, April 18, 2001 7:15 PM
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