i.e. one of our customers (quite a major one) insists on 1.1. compliance for any web servers on their intranet. Therefore usefulness aside, 1.1. is starting to become barrier to adoption.
I'd certainly be interested in getting involved in acheiving 1.1.
PS/ I beleive pipelining offers significant efficiency improvements for SSL connections, i.e. its allows these connections to stay alive, removing a significant per-request overhead. This is very salient in high throughput enviroments such as SMS (GSM text message) handling where the overhead vs the size of an SMS interaction is proportionally significant.
Simon
Nathan Folkman wrote:
[EMAIL PROTECTED]">
In a message dated 11/8/02 10:20:39 AM, [EMAIL PROTECTED] writes:
I have a question regarding the latest 3.5.0 release of AolServer. Does
this version support HTTP 1.1, and more specifically HTTP 1.1 pipelining?
If not, is this planned for the version 4?
HTTP 1.1 is not currently supported, and so far there are no plans for adding support for it to the 4.0 version. To be honest it's been a while since I've looked at the 1.1 spec - what's it all about, and what benefits would there be if we were to support it? Would we need to support all of it, or are there particular parts, such as the pipelining you mention, which would be more beneficial then others?
- n
-- Simon Millward Director OpenMSG Limited +44 (0) 7818 045 801
Tel: +44 (0)1225 48 48 05 Fax: +44 (0)1225 31 6789 Web http://www.open-msg.net Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of OpenMSG Ltd.
