DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16729>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16729 Allow redirects between hosts and ports ------- Additional Comments From [EMAIL PROTECTED] 2003-07-23 11:16 ------- If my understanding is correct without looking at the source code, the purpose of HttpMethodSession is to execute several methods, or one method multiple times, in order to follow redirects. So how about HttpMethodChain or HttpMethodSequence? Or giving it a more personal name, like HttpMethodChainer or HttpRedirector? As for the 'used' flag, does HttpMethodSession have to execute the same HttpMethod object without recycling? If so, you could add a reset() or redirect(URI) method that resets the 'used' flag and performs the other adjustments required to execute the redirect. Or would it be possible to simply recycle the method, just as an application would have to do it? To keep the getters and setters for options out of a class, I like to introduce XxxOptions classes. HttpClientOptions and HttpMethodOptions jump into my mind here. All that remains in the original class is one getter and setter for the options. When overdesigning, one might define an interface with just the getter methods, and a default implementation with getters and setters. Just to point out that the class will not modify the options passed to it :-) Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
