Module uv_iotask

The I/O task runs in its own single-threaded scheduler. By using the interact function you can execute code in a uv callback.

Struct IoTask - Used to abstract-away direct interaction with a libuv loop.
Implementation of Clone for IoTask
Function exit - Shut down the I/O task
Function interact - Provide a callback to be processed by iotask
Function spawn_iotask

Struct `IoTask`

pub struct IoTask {
    async_handle: *ll::uv_async_t,
    op_chan: SharedChan<IoTaskMsg>,
}

Used to abstract-away direct interaction with a libuv loop.

Implementation of `Clone` for `IoTask`

Method `clone`

fn clone(&self) -> IoTask

Function `exit`

fn exit(iotask: &IoTask)

Shut down the I/O task

Is used to signal to the loop that it should close the internally-held async handle and do a sanity check to make sure that all other handles are closed, causing a failure otherwise.

Function `interact`

fn interact(iotask: &IoTask, cb: ~fn(*c_void))

Provide a callback to be processed by iotask

The primary way to do operations again a running iotask that doesn't involve creating a uv handle via safe_handle

Warning

This function is the only safe way to interact with any iotask. Using functions in the uv::ll module outside of the cb passed into this function is very dangerous.

Arguments

iotask - a uv I/O task that you want to do operations against
cb - a function callback to be processed on the running loop's thread. The only parameter passed in is an opaque pointer representing the running uv_loop_t*. In the context of this callback, it is safe to use this pointer to do various uv_* API calls contained within the uv::ll module. It is not safe to send the loop_ptr param to this callback out via ports/chans.

Module uv_iotask

Struct IoTask

Implementation of Clone for IoTask

Method clone

Function exit

Function interact