Thanks for the comments.
Currently, the builder assumes values are already encoded. I think it is a good
idea to have a switcher to control the URL encoding. But do I also need to
allow users to specify which encoding scheme should be used?
Lilu
On Jun 7, 2011, at 6:31 PM, Thom Nichols wrote:
> Are values URL-encoded by the builder or are they assumed to already be
> encoded? You should allow the ability to do both, either by duplicate
> methods like `setPathEscaped` or some funky switching like
>
> builder
> .escaped()
> .setPath("monty%20python")
> .unescaped()
> .addParameter("q","what is your name?")
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
