On 12/22/12 9:15 AM, Michael Neumann wrote:
The best thing I can do is to use blocking I/O here anyway as it's better to have just one connection to Redis and multiplex that, so I can easily use one native thread for that. I am just very new to Rust, and the only thing I found was tcp_net. So I think I should define my own FFI socket calls, right?
Yes, that's what I would do. I think there may be some bindings to BSD sockets in cargo -- Brian would know better here.
The scheduler modes here might be useful to ensure that your task gets its own OS thread: http://dl.rust-lang.org/doc/0.4/core/task.html#enum-schedmode
Patrick _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
