On Wed, Jan 29, 2014 at 3:55 PM, Kevin Ballard <ke...@sb.org> wrote: > Any number of things. > > The use case here is an interactive protocol where writes go in both > directions, and can be initiated in response to external events. The > classic example is an IRC bot. The server can send a message at any time, > so the IRC bot needs to be constantly reading, but writes back to the > socket are not necessarily initiated directly in response to reads, they > may be initiated due to asynchronous operations, or keyboard input at the > terminal, or any number of other external stimuli. >
In this case you'd be waiting on futures from those external events as well. I am assuming that all of I/O would be future-ized, not just TCP streams.
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
