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=10794>. 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=10794 User interaction for authentication [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2004-01-22 13:48 ------- Changelog: * interactive authentication support * another bug fix in NTLMScheme class * InteractiveAuthenticationExample demo app At the moment I opted for keeping credentials callbacks in a static (global) class. I am not sure that this is the best solution, but at the moment I lack better ideas. Do authentication callbacks make sense on per HttpState basis? HttpClient? HttpClientParams? I felt that credentials callbacks should be global in order to avoid multiple authentication dialogs popping up in multithreaded applications, which, in my opinion, would be a bit confusing. At the same time I can well imagine that some may feel differently. Please let me know what you think. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
