Re: [cpp-netlib-devel] soliciting ideas concerning client errors

[John P. F. <jf...@ov...>]

This would replace get() and other applicable base post/put/del/head's.

The deviations would be based off two criteria:
-The specification(ie: rfc1945) by which the request_policy processes 
the request (it's coupled with policy)
-In cases that, while still allowing processing of a get/post() etc, 
would do something counter to what the user expects from the interface, 
such as a unmatched http version or persistence.

John
 
Glyn Matthews wrote:
> Hello John,
>
>
> Firstly, I have noticed a lot of activity in subversion, but I've been so
> far unable to take a look at your work in depth.
>
> 2009/1/10 John P. Feltz <jf...@ov...>
>
>   
>> My solution is to differ that choice to the user on a per request basis.
>> This would be used to express certain server deviations from a protocol
>> standard:
>>     
> <snip />
>   
>> This makes a throw depend on a deviation. In any case, errors up to that
>> point are still pushed to the stack which, with a response fragment,
>> would accompany the exception.
>>
>>     
>
> I think this is good, it gives the client more information about server
> deviations and gives the user more control on how to deal with them.  How do
> you decide what flags to use in the response_deviation struct?  Are you
> proposing this as an overload of the get method or a replacement?
>
>
> Glyn
>
>