Mark - would you be able to explain to me then what your understanding is o=
f the =0Aintended use of chunk extensions within HTTP?=0A=0AI understand wh=
at you are saying and I understand I may be pushing boundaries =0Awith what=
I am doing here and may write some of my own stuff for this purpose =0Ahow=
ever the extensions look like a useful feature anyway so I'd be interested =
in =0Aknowing your opinion on them.=0A=0A=0A=0A=0A_________________________=
_______=0AFrom: Mark Thomas <markt@apache.org>=0ATo: Tomcat Users List <use=
rs@tomcat.apache.org>=0ASent: Wednesday, 5 January, 2011 14:58:55=0ASubject=
: Re: Tomcat and HTTP chunk extensions=0A=0AOn 05/01/2011 14:52, EOIN MCQUI=
LLAN wrote:=0A> Mark - maybe I am pushing the boundaries with what I am doi=
ng here however =0A>given =0A>=0A> the HTTP RFC provides us with a chunk ex=
tension capability then I would have =0A> assumed there would exist an set =
of API calls within Tomcat that allow us to =0A> read/write a chunk extensi=
on?=0A=0AYour assumption is wrong. There is no such API.=0A=0AThe HTTP prot=
ocol does not allow for client/server during a=0Arequest/response. The clie=
nt sends a request message, the server replies=0Awith a response message. T=
hat is all you have to work with.=0A=0ATo repeat what I wrote before. Chunk=
ing is a transfer encoding. It=0Aapplies *per link*, not end to end.=0A=0AM=
ark=0A=0A------------------------------------------------------------------=
---=0ATo unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org=0AFor add=
itional commands, e-mail: users-help@tomcat.apache.org
|