Same here, I am highly interested in the topic. On Jul 5, 2014 10:14 AM, "Nat Pryce" <[email protected]> wrote:
> I've been trying to write tasks that wait for both I/O and channel > communication. I've been told that, to maximise communication performance, > channels do not support selecting of both channels and I/O objects. > Therefore a program should signal to a task that is waiting for I/O over > another I/O object, such as a pipe, not by sending a message over a > channel. Fair enough. > > What API should I use to wait for multiple I/O objects within a task? Is > there a runtime-independent API for this? > > And if I write my own I/O abstractions, for example around eventfd on > Linux, what traits (platform specific traits, I imagine) should I implement > to make them work with the runtime-independent I/O select API? > > Sorry if this is already covered in the documentation. I've searched but > not found anything obvious. > > Any help much appreciated. > > --Nat > > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > >
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
