In my personal view HTTP/1.1 is for performance demanding, resource competing, asynchronously multi-threading servers and clients, where the tricks introduced really pay off.
HTTP/1.0 is necessarily sufficient solution for things done reliably one at a time for the job at hand. So it's balance of complexity and usefulness is ideal for application development. Web browsers, web servers, high performance gateways are not applications, they are platforms. --- Stefano Lanzavecchia <[EMAIL PROTECTED]> wrote: > > chunk in HTTP/1.1 is really troublesome, thus is there any good reason > > to send a > > HTTP/1.1 request? > > Well... the reasons why HTTP/1.1 was created in the first place. There used > to be a page on http://www.w3c.org/ where the rationale was explained. I > cannot find it anymore but it's not surprising given that the version 1.1 of > the standard is almost 10 years old. One of the main points I remember was > socket reuse: while in HTTP/1.0 the socket is discarded at the end of every > reply, it can (and should: > http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1) be reused in > HTTP/1.1. > Also, it's possible to make conditional requests > (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5) which > reduce the net traffic. > > I agree, though, that properly implementing HTTP/1.1 is a real pain, both > for a client and for a server. I will probably try to implement a subset of > it soon (in APL, though). Wish me luck ;) > > -- > WildHeart'2k6 - mailto:[EMAIL PROTECTED] > My digipics and blogs: http://wildy2k5.spaces.live.com/ > > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
