[go-nuts] Re: bufio.Writer and timeouts

2017-09-14 Thread Juliusz Chroboczek
> Hmm maybe I misunderstood your use case. I thought you were basically > setting a fixed write duration via SetWriteDeadline() before each Write() > call, in which case the same treatment probably should be done for Flush(). I'm already doing that. -- You received this message because you are

Re: [go-nuts] Re: bufio.Writer and timeouts

2017-09-14 Thread Sangjin Lee
Hmm maybe I misunderstood your use case. I thought you were basically setting a fixed write duration via SetWriteDeadline() before each Write() call, in which case the same treatment probably should be done for Flush(). Sangjin On Thu, Sep 14, 2017 at 3:33 PM, Juliusz Chroboczek

[go-nuts] Re: bufio.Writer and timeouts

2017-09-14 Thread Juliusz Chroboczek
> Is extending the deadline right before flushing an option? No. Before the Flush (or the Write) times out, I don't know that this particular peer is congested, and hence I have no reason to reschedule requests queued to this peer on a different connection. -- Juliusz -- You received this

[go-nuts] Re: bufio.Writer and timeouts

2017-09-11 Thread Sangjin Lee
Is extending the deadline right before flushing an option? If your deadline is based on a relative duration, you could apply the same delay on Flush() too because Flush() may incur write, no? On Saturday, September 9, 2017 at 8:17:24 AM UTC-7, Juliusz Chroboczek wrote: > > > bufio.Writer is

[go-nuts] Re: bufio.Writer and timeouts

2017-09-09 Thread Juliusz Chroboczek
> bufio.Writer is about 200 lines, and you probably don't even need all > of them. Just copy it and modify it for your purposes. Ok, thanks. -- Juliusz -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop