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 11111 invoked from network); 6 Feb 2001 21:07:13 -0000 Received: from e24.nc.us.ibm.com (HELO outside) (32.97.136.230) by h31.sny.collab.net with SMTP; 6 Feb 2001 21:07:13 -0000 Received: from southrelay02.raleigh.ibm.com (southrelay02.raleigh.ibm.com [9.37.3.209]) by outside (8.9.3/8.9.3) with ESMTP id QAA15150 for ; Tue, 6 Feb 2001 16:08:11 -0600 Received: from d04nm204.raleigh.ibm.com (d04nm204.raleigh.ibm.com [9.67.228.13]) by southrelay02.raleigh.ibm.com (8.11.2/NCO v4.95) with ESMTP id f16L7EW22358 for ; Tue, 6 Feb 2001 16:07:14 -0500 Importance: Normal Subject: Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2) To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Doug Davis" Date: Tue, 6 Feb 2001 16:07:10 -0500 X-MIMETrack: Serialize by Router on D04NM204/04/M/IBM(Release 5.0.3 (Intl)|21 March 2000) at 02/06/2001 04:07:14 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N If I remember correctly chunking is just dividing up the output into smaller pieces (chunks) where each chunk has it's own content-length. This way the client doesn't need an overall content-length, it just keep reading chunks until it gets one that has a length of zero. data data 0 <- zero -Dug "Sanjiva Weerawarana" on 02/06/2001 02:16:59 AM Please respond to axis-dev@xml.apache.org To: cc: Subject: Re: streaming outbound messages (was Re: [Vote] 1 Msg or 2) Hi Alex, > i agree that it is good to have multiple interfaces to access inbound message. > > i would put them in this order: > * pull parser or MessageElement/XMLElement (as proposed by James Snell) > * SAX as it is easy to convert pull parser XML events into SAX events > * DOM or JDOM as it can always be built from SAX events or pull parser events This is a good list and I agree with the priority ordering! > however i think that streaming outbound messages in HTTP/1.0 is almost impossible > and not that useful as to create valid POST it is necessary to known > Content-length - i do not know other way to do it (and get through HTTP > proxies...) maybe except creating invalid POST request without Content-length... > > 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. Sanjiva.