If I understand the meaning, then I would tend to make the exception
scenario mean "something is fundamentally wrong with the service", rather
than "your request was invalid". The latter scenario is better handled by
allow an error message as part of the standard API - which could be anything
from a simple Status enum, a basic ErrorMessage string, or anything else you
can envisage.

Marc

On 1 August 2011 09:59, lasse <l...@schouw.me> wrote:

> How do I report Exceptions back to the http Client?
> I am running a HttpServer that implements the IBasicService interface and
> when exceptions are throw on the server I get this error on the client.
> System.Net.WebException: The **remote server returned an **
> error: (400) Bad Request.
>
> Lasse
>
> --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/protobuf/-/DIcMtydglOoJ.
> To post to this group, send email to protobuf@googlegroups.com.
> To unsubscribe from this group, send email to
> protobuf+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>



-- 
Regards,

Marc

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to 
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/protobuf?hl=en.

Reply via email to