On 4/11/13 2:36 PM, Jeremy Huffman wrote:
Hi,
I am considering Rust for a particular use case in which I would be
doing lots of concurrent requests that would spend most of their time
blocked on network I/O in foreign C calls. I may be mistaken but I
think a task that blocks like this would block any other tasks on the
same scheduler - is that correct? What would perhaps be a good solution
would be something like a task pool in which each task runs in a
separate OS thread - is there a straightforward way to achieve this?
There is `std::task_pool` for this purpose. There is an example of this
use case in the test case in that file.
Patrick
_______________________________________________
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
