Return-Path: Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 76158 invoked from network); 7 Feb 2001 00:37:12 -0000 Received: from mplspop2.mpls.uswest.net (204.147.80.4) by h31.sny.collab.net with SMTP; 7 Feb 2001 00:37:12 -0000 Received: (qmail 33874 invoked from network); 7 Feb 2001 00:37:17 -0000 Received: from dialupc244.mpls.uswest.net (HELO pop.mpls.uswest.net) (207.225.142.244) by mplspop2.mpls.uswest.net with SMTP; 7 Feb 2001 00:37:17 -0000 Date: Tue, 06 Feb 2001 18:33:52 -0600 Message-ID: <3A8097EF.D6D7EDD2@pop.mpls.uswest.net> From: "George I Matkovits" To: axis-dev@xml.apache.org Reply-To: matkovitsg@uswest.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {U S WEST.net} (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 Subject: Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2) References: <020e01c08d21$333c2230$6e02a8c0@watson.ibm.com> <3A7F9586.E538D008@cs.indiana.edu> <000901c0900c$dbac66d0$6e02a8c0@watson.ibm.com> <3A802808.26E3BD90@cs.indiana.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N 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)