Mark I'm not sure I fully agree with your last answers. The purpose, to me,=
=0Awould be to extend the capabilities of chunked transfer encoding rather=
than to =0Aimplement chunked transfer encoding. They are optional after al=
l. Being optional =0Athen I would view them moe as a feature or extension b=
ut this is merely wording =0Aso I am splitting hairs here.=0A=0AI appreciat=
e the time you've taken to reply on this.=0A=0AThanks=0A Eoin=0A=0A=0A=0A=
=0A________________________________=0AFrom: Mark Thomas <markt@apache.org>=
=0ATo: Tomcat Users List <users@tomcat.apache.org>=0ASent: Wednesday, 5 Jan=
uary, 2011 16:39:31=0ASubject: Re: Tomcat and HTTP chunk extensions=0A=0AOn=
05/01/2011 15:21, EOIN MCQUILLAN wrote:=0A> Mark - would you be able to ex=
plain to me then what your understanding is of =0A>the =0A>=0A> intended us=
e of chunk extensions within HTTP?=0A=0ATo implement chunked transfer encod=
ing.=0A=0A> I understand what you are saying and I understand I may be push=
ing boundaries =0A> with what I am doing here and may write some of my own =
stuff for this purpose =0A> however the extensions look like a useful featu=
re anyway so I'd be interested =0A>in =0A>=0A> knowing your opinion on them=
.=0A=0AChunked extentions are not a feature. They are a component part of=
=0Achunked transfer encoding.=0A=0AMark=0A=0A> =0A> =0A> =0A> =0A> ________=
________________________=0A> From: Mark Thomas <markt@apache.org>=0A> To: T=
omcat Users List <users@tomcat.apache.org>=0A> Sent: Wednesday, 5 January, =
2011 14:58:55=0A> Subject: Re: Tomcat and HTTP chunk extensions=0A> =0A> On=
05/01/2011 14:52, EOIN MCQUILLAN wrote:=0A>> Mark - maybe I am pushing the=
boundaries with what I am doing here however =0A>> given =0A>>=0A>> the
HT=
TP RFC provides us with a chunk extension 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 extension?=0A> =0A> Your assumption is wrong. =
There is no such API.=0A> =0A> The HTTP protocol does not allow for client/=
server during a=0A> request/response. The client sends a request message, t=
he server replies=0A> with a response message. That is all you have to work=
with.=0A> =0A> To repeat what I wrote before. Chunking is a transfer encod=
ing. It=0A> applies *per link*, not end to end.=0A> =0A> Mark=0A> =0A> ----=
-----------------------------------------------------------------=0A> To un=
subscribe, e-mail: users-unsubscribe@tomcat.apache.org=0A> For additional c=
ommands, e-mail: users-help@tomcat.apache.org=0A=0A=0A---------------------=
------------------------------------------------=0ATo unsubscribe, e-mail: =
users-unsubscribe@tomcat.apache.org=0AFor additional commands, e-mail: user=
s-help@tomcat.apache.org
|