Great thanks! And i guess the OS handles cooridnating read and write operation on same socket / stream right?
On Tuesday, September 5, 2017 at 11:34:41 AM UTC+3, Ben Noordhuis wrote: > > On Mon, Sep 4, 2017 at 5:51 PM, <[email protected] <javascript:>> wrote: > > Hi, > > I'm building a simple tcp client with an api which sends request to > server > > and gets response asynchronously. > > Now, in the init of the client i call Read_start with CB (onread). Once > the > > onread callback finishes to read some kind of response (might be several > > chunks) it starts async thread to process it. > > But mean while there might be multiple write request - should i call > > ReadStop? there might be more responses from the server during those > times > > and i don't want to lose them. > > You can call uv_read_stop() if you want to rate-limit incoming > traffic, but you don't have to. It won't affect write operations. > -- 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.
