My comments are fairly developer oriented rather than user oriented, so unless you want to get in and work on the Slide code, I can't really help you.
Having said that, I think Slide would be better off with HttpMultiClient as it provides for persistent connections better and one client instance could be shared throughout Slide which makes tracking authorization credentials a lot simpler as well as better performance (it can take advantage of Http1.1 keep alive) and a fair few other little things that really add up. Mostly though HttpMultiClient just seems to fit into the way slide works a lot better than HttpClient (but HttpMultiClient doesn't exist in the version of HttpClient that is in use by Slide to my knowledge). The concept of storing all session information in the URL breaks down with NTLM authentication as there is no standard way of doing it and one login will always work for the entirety of a server. The latest version of HttpClient has very good methods for dealing with this but they don't come through the Slide API too well and the fact that Slide keeps creating new HttpClient's makes it even more difficult as you can't just set the credentials on the internal HttpClient and leave it be. There are plenty of very talented people working on Slide and when a stable release of HttpClient comes out I'm sure they'll start working to get back in sync with the commons version. I'll probably have to revisit this issue at some point as we start to expand our use of WebDAV but for now I can't afford to work on Slide any longer. Adrian Sutton, Software Engineer Ephox Corporation www.ephox.com This email and any files transmitted with it are confidential and intended solely for the use of the individual to whom they are addressed. Opinions contained in this email do not necessarily reflect the opinions of Ephox Corporation. If you have received this email in error please notify the sender immediately and delete all copies of the correspondence from your computer and/or computer network. No warranty is given that this message upon its receipt is virus free and the sender in this respect accepts no liability. -----Original Message----- From: Sung-Gu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 2 October 2002 4:13 PM To: Slide Users Mailing List Subject: Re: Client problems with userinfo ----- Original Message ----- From: "Adrian Sutton" <[EMAIL PROTECTED]> > >(It will be supported, when the client is integrated with HttpClient 2.0) > > If it will help you any, I have started to make this transition, however I I'm not sure yet... > a. I went about it the wrong way. Slide would be better off moving to What do you mean by the wrong way? --a > HttpMultiClient instead of trying to stick with HttpClient. I wound up Why? > having to put in a fair few hacks to make it all work - particularly since > NTLM authentication requires NTCredentials (which includes a host and > domain) and not just UsernamePasswordCredentials Reasonable... in general, a session information is like URI-formed like, it might include even each path information and could be differed from each... Because possbilly it could be set like that on the server... > since it turned out to be more difficult than I first imagined. I see. :) Sung-Gu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
