On Tue, Jan 03, 2006 at 11:29:12AM -0500, Rob Manning wrote: > Oleg Kalnichevski wrote: > > >On Tue, Jan 03, 2006 at 10:38:41AM -0500, Rob Manning wrote: > > > > > >>Hello, > >> > >>Is there a public API method that one can call to get a string (or > >>something) that > >>indicates the version of HttpClient in use? (3.0rc1, 3.0rc2, 3.0, etc...)? > >> > >> > >> > > > >Rob, > >No, there is not. Why would you want such method in the first place? > > > > > For troubleshooting our applets in the field. Our product uses an > applet and HttpClient to connect to > the server that the applet is being served from. When we are trying to > troubleshoot an issue, we > could use the product version to connote the version of HttpClient that > was shipped with the product. > However, it would be nice to just print it out in the debug log.(I > suppose we could hard-code the > version into our product, but that just seems like the wrong thing to > do. Most software I've used has > some class that indicates the version of the app or library. It also > makes runtime dependency checking > possible) > > Rob
Rob, You can use the user-agent header for that end. The User-Agent header set by HttpClient per default always includes the release version. However, if you own the deployment process why do not you simply deploy the desired version of HttpClient? If you seriously want to make sure you are dealing with a specific library or a specific version you should consider digitally signing all your dependencies Oleg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
