tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From EOIN MCQUILLAN <eoin.mcquil...@btinternet.com>
Subject Re: Tomcat and HTTP chunk extensions
Date Wed, 05 Jan 2011 17:02:42 GMT
Mark I'm not sure I fully agree with your last answers. The purpose, to me, 
would be to extend the capabilities of chunked transfer encoding rather than to 
implement chunked transfer encoding. They are optional after all. Being optional 
then I would view them moe as a feature or extension but this is merely wording 
so I am splitting hairs here.

I appreciate the time you've taken to reply on this.

Thanks
  Eoin




________________________________
From: Mark Thomas <markt@apache.org>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Wednesday, 5 January, 2011 16:39:31
Subject: Re: Tomcat and HTTP chunk extensions

On 05/01/2011 15:21, EOIN MCQUILLAN wrote:
> Mark - would you be able to explain to me then what your understanding is of 
>the 
>
> intended use of chunk extensions within HTTP?

To implement chunked transfer encoding.

> I understand what you are saying and I understand I may be pushing boundaries 
> with what I am doing here and may write some of my own stuff for this purpose 
> however the extensions look like a useful feature anyway so I'd be interested 
>in 
>
> knowing your opinion on them.

Chunked extentions are not a feature. They are a component part of
chunked transfer encoding.

Mark

> 
> 
> 
> 
> ________________________________
> From: Mark Thomas <markt@apache.org>
> To: Tomcat Users List <users@tomcat.apache.org>
> Sent: Wednesday, 5 January, 2011 14:58:55
> Subject: Re: Tomcat and HTTP chunk extensions
> 
> On 05/01/2011 14:52, EOIN MCQUILLAN wrote:
>> Mark - maybe I am pushing the boundaries with what I am doing here however 
>> given 
>>
>> the HTTP RFC provides us with a chunk extension capability then I would have 
>> assumed there would exist an set of API calls within Tomcat that allow us to 
>> read/write a chunk extension?
> 
> Your assumption is wrong. There is no such API.
> 
> The HTTP protocol does not allow for client/server during a
> request/response. The client sends a request message, the server replies
> with a response message. That is all you have to work with.
> 
> To repeat what I wrote before. Chunking is a transfer encoding. It
> applies *per link*, not end to end.
> 
> Mark
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message