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 <j...@irif.fr> wrote: > > 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 message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/to > pic/golang-nuts/y0lHtwaeeQk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
