DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=16124>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=16124 isHttp11 should have HttpClient scope ------- Additional Comments From [EMAIL PROTECTED] 2004-04-30 12:58 ------- > We have requests to support HTTP version parameterization on a per connection > basis, which I also find quite reasonable. Where would you see the version saved? I agree that the request seems reasonable. My concern is how we implement it. As you mention in your previous message a viable solution to this problem is not readily apparent. Here are the problems that we need to solve, as I see it: - We need somewhere to store the version supported by a connection. My preference would be to add a property to the connection itself. - We need a way to determine what versions a connection supports. As you have mentioned, just because a connection is used for HTTP 1.0 does not mean that it can't also be used for HTTP 1.1. I see two options here. 1) Assume a connection can be used for all HTTP versions, unless a particular version is rejected. Defaults to accept all. 2) The first use of a connection defines the version it can be used for. - A connection's version is determined outside of the HttpConnection class. We must rely on the HttpMethod to set the supported version on the connection. This is not a major issue as we have control over the HttpMethodBase, but it's a little nasty. I will do some brainstorming and see if I can come up with any new ideas. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
