More Pros:
- Our multipart POST implementation is quite poor (only one file per request, for example). HTTPClient's should hopefully be more complete.
- Unit testing: HttpClient comes with a test webapp, that we could use to write equivalent JMeter tests.
The Con you mention:
2. HTTPClient contains similar objects like Cookie
Is actually a Pro: our CookieManager implementation is somewhat buggy (at least in terms of standard's compliance). Switching to HTTPClient's cookie management would hopefully fix most of these.
-- Salut,
Jordi.
peter lin wrote:
yeah you're right sebastian. for some odd reason, even though GetMethod/PostMethod extend HttpMethodBase, it (the addHeader) didn't show up in eclipse.
I'll take a closer look. tomcat's manager webapp doesn't support digest correctly, or I can't get HTTPClient to authenticate.
hopefully I'll get more familiar with it and see if we really benefit from using it.
peter lin
--- [EMAIL PROTECTED] wrote:
Pros: 4. Should be able to re-use connections, so can implement proper keep-alive.
As to Con: 1 - Doesn't HttpMethod give access to headers?
I guess I should give it a try ...!
S.
----- Original Message ----- From: "peter lin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 12, 2004 3:49 PM
Subject: finding on HTTPClient
Here's what I found so far trying to use HTTPClient for the monitor.
Cons: 1. the current release candidate doesn't have an easy way to set the HTTP headers 2. HTTPClient contains similar objects like Cookie 3. Using HTTPClient would mean refactoring HTTPSampler
Pros: 1. HTTPClient supports digest auth and NTLM 2. the API is relatively simple and easy to use 3. it uses raw sockets
I haven't performed any benchmarks and not sure it would make much difference. Right now it's not clear to me there's enough advantage. Originally I thought the monitor would have to support digest auth, but it looks like Tomcat's /manager/status servlet doesn't handle digest auth correctly. I wasn't able to get HTTPClient or internet explorer to authenticate against the manager webapp when I set it to "digest".
It looks like the current HTTPSampler is sufficient for the monitor, so I'm inclined to just stick with what we have. I like how we handle HTTP headers and don't really feel like patching HTTPClient.
peter lin
--------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
--------------------------------------------------------------------- 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]
