cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: Retuning Sitemap Design
Date Mon, 14 Jan 2002 22:04:46 GMT
On Fri, 11 Jan 2002, Stefano Mazzocchi wrote:

> Gerhard Froehlich wrote:
>
> > >> > <question who="SM">what happens when the client has already
received
> > >> > part of the request (say during aggregation?)</question>
> > >>
> > >> The discussion had taken place on this, intermediate output stream was
> > >> suggested to avoid "committed response":
> > >> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99828709211581&w=2
> > >> and
> > >> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=99442091111980&w=2
> > >
> > >Hmmmm, did you guys thought about using 'chuncked HTTP'?
> >
> > Could you explain, what do you exactly mean with 'chuncked HTTP'?
>
> Go and RTFM :)
>
> No, seriously, take a look at
>
>  ftp://ftp.isi.edu/in-notes/rfc2616.txt
>
> and search for 'chunk'. You'll find that HTTP/1.1 has the ability to
> 'chunk' (split) the response in several parts, each one with a header.
>
> This was designed exactly to allow servers to return error messages
> *after* the original header has been sent. The problem is that the
> Servlet API doesn't allow chunking by itself, so we must *reencode* the
> chunks in the servlet output stream
>
> I just sent a question to my friends part of the Servlet Expert Group at
> the JCP but as long as I was there, nobody touched the argument.
>
> Comments?

Chunking should best happend transparently to a Servlet
(as an option of the Servlet engine). Is there a need to state chunking
programmatically?

Unfortunately I don't know if Catalina/Tomcat (or any other Servlet
engine) is supporting this transfer coding.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message