axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Snell <jmsn...@intesolv.com>
Subject RE: streaming outbound messages (was Re: [Vote] 1 Msg or 2)
Date Wed, 07 Feb 2001 01:44:49 GMT
Yeah... that's the problem with streaming... ;-) 

- James

> -----Original Message-----
> From: Doug Davis [mailto:dug@us.ibm.com]
> Sent: Tuesday, February 06, 2001 4:45 PM
> To: axis-dev@xml.apache.org
> Subject: Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2)
> 
> 
> Just wondering... let's say we get everything streaming and let's say
> that its soooo good that the outgoing message actually starts to leave
> the last handler before the before all other handlers are done.  And
> let's say that one of the handlesr (not the last one in the 
> chain) throws
> a fault.  At this point the transport listener (or sender depending on
> how you look at things) has already send back an rc of 200 but it
> really needs to be a non-ok rc, doesn't it?  How does this 
> get handled?
> -Dug
> 
> 
> "George I Matkovits" <matkovitsg@uswest.net> on 02/06/2001 07:33:52 PM
> 
> Please respond to axis-dev@xml.apache.org
> 
> To:   axis-dev@xml.apache.org
> cc:
> Subject:  Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2)
> 
> 
> 
> Yes, the later Tomcat versions support chunking. Over an URL 
> connection
> (will support
> 500 codes correctly with Java2V1.4, the 2 years old 
> URLconnection bug is
> finally
> going to be fixed :-)  HTTP/1.1 support can easily be put 
> even into the
> current Soap
> V2.1+. It should also work in AXIS, since an HTTP/1.1 URL 
> connection will
> support
> correctly not only JSP/Servlet sessions but also chunking.
> Regards - George
> 
> Aleksander Slominski wrote:
> 
> > Sanjiva Weerawarana wrote:
> >
> > > > it would be still possible with HTTP/1.1 chunking but i 
> have not seen
> it on
> > > the
> > > > list of things to do for AXIS ARCH (or I may be wrong...).
> > >
> > > Can u please explain how HTTP chunking works and how that 
> can be used
> > > to do outbound streaming? I think that could have a major 
> performance
> > > impact.
> >
> > when HTTP/1.0 POST is used as defined in SOAP spec 1.1 it 
> is necessary to
> > calculate Content-Length before starting sending anything 
> and it means
> that we
> > need to keep an output buffer in memory (to calculate 
> content length).
> >
> > with HTTP/1.1 chunking it is possible to start sending as 
> soon as we have
> > something serialized and more important - we do not need to keep the
> output
> > buffer in memory! however to have it working both sides - client and
> server -
> > must implement chunking. i think that apache has support for it so
> running tomcat
> > <-> apache will give chunking support but we still need to 
> have it on
> client side
> > to work...
> >
> > for details please on chunking please see
> > http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1
> >
> > thanks,
> >
> > alek
> > --
> > Aleksander Slominski, LH 316, IU, 
> http://www.extreme.indiana.edu/~aslom
> > As I look afar I see neither cherry Nor tinted leaves Just 
> a modest hut
> > on the coast In the dusk of Autumn nightfall - Fujiwara no Teika
> (1162-1241)
> 
> 
> 
> 

Mime
View raw message