On Mon, May 23, 2016 at 5:17 AM, Peng Zheng <[email protected]> wrote: > Hi, > > Consider the following scenario: > A video encoder keeps feeding H.264 bitstream into a network streaming > buffer, which several network connections shared. > The buffer is 'leaky' in the sense that the most dated video frame will be > overwritten by the encoder. This leaky feature > is necessary, since network conditions vary from connection to connection. > For performance reason, each time > we write 8K bytes. > > To accommodate slow network connection, when the buffer is about to leak, we > need to cancel the current pending > write request (if any) on the slowest connection. Reading through the > documentation, I have no clue of how to do this. > The source code of uv_try_write implies that it might be done. > > Does the above use case justify an extension the uv_cancel? > > PS: libuv is great.
A pull request that teaches libuv how to cancel uv_write_t requests would be welcome. The reason it hasn't been done so far (IIRC) is that it's difficult to implement on Windows. We generally don't add features unless they are implemented on all platforms. -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
