axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dasarath Weeratunge <dasarathweeratu...@yahoo.com>
Subject RE: [Axis2] Can OM with differed building really be so effective in Axis2?
Date Mon, 04 Apr 2005 05:21:10 GMT
Further, even thought we are using StAX at the moment
the goal of axis2 team is to move to tStAX as soon as
possible. tStAX is a typed-StAX API which allows us to
directly convert contents of the underlying byte
stream into relevant types without having to first
convert into strings.

--dasarath


--- Chathura Herath <chathura@opensource.lk> wrote:
> Hi Eran, HaoRan Zheng,
> 
> One more thing.. There is another point that will
> give us a performance
> improvement. If our data binding tool is working on
> StAX or SAX, which I
> believe we are and will, then we ll have a direct OM
> pull stream --> Java
> Object conversion. There will be no intermediary
> object model such as DOM .
> This will be desirable for our performance. 
> 
> Regards,
> Chathura
> 
> 
> 
> > -----Original Message-----
> > From: HaoRan Zheng [mailto:hrzheng@gmail.com]
> > Sent: Monday, April 04, 2005 8:45 AM
> > To: axis-dev@ws.apache.org;
> chinthaka@opensource.lk
> > Subject: Re: [Axis2] Can OM with differed building
> really be so effective
> > in Axis2?
> > 
> > Thank you Eran, so much!
> > 
> > There is another thing I want to make sure. Is
> "differed building" a
> > clerical error? Should it be "deferred building",
> or it has different
> > meaning? I see the former expression full of the
> Axis2 documents, such
> > as architecture guide and AXIOM tutorial.
> > 
> > On Apr 4, 2005 10:19 AM, Eran Chinthaka
> <chinthaka@opensource.lk> wrote:
> > >
> > > Re-sending with [Axis2] prefix
> > > >
> > > > Hi all,
> > > >
> > > > Sorry for bothering everybody. I'm not sure
> whether this question is
> > > > appropriate for this maillist. If not, please
> apprise me and I'll
> > > > never commit it again:)
> > > >
> > > > I'm very interested in Axis2 and I know
> performance is a big goal of
> > > > Axis2. But, I really wonder whether the
> differed building can help to
> > > > enhance the performance a lot AT SERVER SIDE.
> My suspicion is based on
> > > > the follow  points:
> > > >
> > > > (a). Almost all the SOAP services need the
> parsed SOAP envelope (the
> > > > echoXML sample service maybe an exception), so
> differed building does
> > > > not mean no building. That is to say, parsing
> and building is
> > > > unavoidable mostly.
> > > > (b). At server side, we won't design any
> unnecessary arguments. So we
> > > > need parse the SOAP message entirely; even
> partial parsing won't be
> > > > feasible at server side.
> > > >
> > > > I know it is an improvement to choose the
> pull-parsing with StAX. At
> > > > least it is one-time parsing while Axis 1.x
> used the replay mechanism
> > > > to process the pre-parsed SAX events. But I do
> want to know, how much
> > > > performance enhancement can benefit from the
> OM with differed
> > > > building? Could anyone explain it to me? Thank
> you so much!
> > > >
> > > > Regards,
> > > > HR, Zheng
> > >
> > >
> 
> 
> 
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

Mime
View raw message