Mark - maybe I am pushing the boundaries with what I am doing here however =
given =0Athe HTTP RFC provides us with a chunk extension capability then I =
would have =0Aassumed there would exist an set of API calls within Tomcat t=
hat allow us to =0Aread/write a chunk extension?=0A=0A=0A=0A=0A____________=
____________________=0AFrom: Mark Thomas <markt@apache.org>=0ATo: Tomcat Us=
ers List <users@tomcat.apache.org>=0ASent: Wednesday, 5 January, 2011 14:32=
:56=0ASubject: Re: Tomcat and HTTP chunk extensions=0A=0AOn 05/01/2011 14:2=
9, EOIN MCQUILLAN wrote:=0A> Thanks for the reply Andr=E9.=0A> =0A> I am ta=
king my terminology from RFC 2616 so "chunk-extension" should be the =0A> r=
ight terminology I think.=0A> =0A> I don't think multiparting would be the =
way to go in this case. Really with the =0A>=0A> chunking extensions the id=
ea for me would be to mid-request be able to =0A> communicate between clien=
t and server.=0A=0AThat is simply not possible in a single HTTP request/res=
ponse. In=0Aaddition, chunking is a transfer encoding and therefore only a=
pplies per=0Alink.=0A=0ASounds like you really need to be using Comet.=0A=
=0AMark=0A=0A--------------------------------------------------------------=
-------=0ATo unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org=0AFor=
additional commands, e-mail: users-help@tomcat.apache.org
|