commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amir D. Kolsky" <>
Subject RE: [HTTPCLIENT] Suggestion: Uniform parameter handling
Date Wed, 24 Apr 2002 15:22:27 GMT
I agree that it should be done. Don't forget the get on the request body... This is required
when you pass HttpMethods from one handler to another and you'd like to treat it as a container.

-----Original Message-----
From: Rainer Klute []
Sent: Wed, April 24, 2002 10:59 AM
Subject: [HTTPCLIENT] Suggestion: Uniform parameter handling

Currently there is no common or comfortable mechanism to read 
an HttpMethod's parameters. You can get and set the query 
string, but this is reasonable with GET only. Parsing the query 
string into parameters is not supported by httpclient - at 
least as far as I know. This is a task left to each application.

PostMethod is even worse because you can only *modify* 
parameters (set, add, remove) but you have no chance to 
*get* them.

Setting, adding, removing and getting parameters should be 
supported in a uniform way by all HttpMethod implementations, at 
least by GET and POST. I propose to enhance the HttpMethod 
interface by method specifications for these tasks and to 
provide default implementations in HttpMethodBase.

I am willing to implement them, but we need consensus here, 
because this change introduces new methods in an interface and 
thus breaks applications that implement HttpMethod directly 
without subclassing HttpMethodBase.

What do you think?

Best regards
Rainer Klute

                           Rainer Klute IT-Consulting GmbH i. Gr.
  Rainer Klute             E-Mail:
  K├Ârner Grund 24          Telefon: +49 172 2324824
D-44143 Dortmund           Telefax: +49 231 5349423

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message