On Fri, Aug 26, 2016 at 5:46 AM, <siliang....@grabtaxi.com> wrote:

> I found it's hard to match *this particular error (*"broken pipe"*)*, and
> handle it accordingly, is there a solution?
>


What do you want to do with this particular error? How would you handle it
differently than any other permanent error?

The error is exactly the same as you would encounter using the C socket
api, on linux it's syscall.EPIPE.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to