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=25529>. 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=25529 Redesign of HTTP authentication framework ------- Additional Comments From [EMAIL PROTECTED] 2004-01-12 13:36 ------- > I think the patch is okay, but the architecture is not perfect yet. You can > still commit it I guess. I did not run any tests on it but rather scimmed the > code. Things can be always done better. The question is if the patch is step forward or backward. If you need more time to review the patch, let me know. > 2. For real stateful authentication we will need a single AuthScheme instance > that lives during a complete authentication cycle. Unless we are talking about different things, I believe that this is in fact the case. There's _always_ (preemptive auth scheme notwithstanding) only one instance of authentication scheme within a complete authentication cycle. One may take this one step further and persist (cache) authentication schemes between method invocations to avoid re-authentication against the realms HttpClient already has authenticated with. But this is something for 4.0 Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
