Re: [cpp-netlib-devel] Comments about the HTTP client interface

[K. G. <kim...@gm...>]

Hi Dean,

On Thu, Aug 28, 2008 at 09:25, Dean Michael Berris
<mik...@gm...> wrote:
>
> If helping the developer avoid shooting themselves in the foot matters
> (which I really think does, a lot) then keeping the static mapping and
> semantics intact would be a good premium. I'd think it's more a
> feature than a deficiency that the HTTP client allows for an
> expressive interface to allow users to "say what they mean" instead of
> leaving a wide open door to allow users to easily get things wrong.

Yep, I agree with that. Though I also think there's value in a
data-driveable interface -- I keep finding myself having to switch on
a set of constants in order to invoke a specific method, whose only
raison d'etre is to encapsulate the same constant values. I think
that's why I like this *as a complement*. There's no doubt in my mind
that the most common usage is simply client::get/post.

Then again, the only case I can see where the verb would vary like
that is some sort of HTTP inspector application, where you can work
from a set of headers and a body and invoke different verbs to see how
a web server reacts. It's still doable with the existing interface,
just clunkier.

Never mind me ;-)

- Kim