> > From browsing the internet I got the impression that this sequence of events > > is possible: > > > > alloc_cb(); > > alloc_cb(); > > read_cb(); > > read_cb();
That's possible although it would be for different handles. E.g. this could happen: > > alloc_cb(handle1); > > alloc_cb(handle2); > > read_cb(handle1); > > read_cb(handle2); But this isn't: > > alloc_cb(handle1); > > alloc_cb(handle1); > > read_cb(handle1); > > read_cb(handle1); - Bert > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Iñaki Baz Castillo > Sent: Tuesday, June 03, 2014 5:46 PM > To: [email protected] > Subject: Re: [libuv] interleaved alloc_cb/read_cb, is the libuv test wrong or > did I > misunderstand? > > 2014-06-03 17:42 GMT+02:00 Nicolas Hillegeer <[email protected]>: > > From browsing the internet I got the impression that this sequence of events > > is possible: > > > > alloc_cb(); > > alloc_cb(); > > read_cb(); > > read_cb(); > > Never seen that under Linux and OSX when using libuv TCP and PIPE handles. > > > -- > Iñaki Baz Castillo > <[email protected]> > > -- > 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 http://groups.google.com/group/libuv. > For more options, visit https://groups.google.com/d/optout. -- 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 http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
