Struct libuv::handles::poll::PollHandle
source · pub struct PollHandle { /* private fields */ }
Expand description
Poll handles are used to watch file descriptors for readability, writability and disconnection similar to the purpose of poll(2).
The purpose of poll handles is to enable integrating external libraries that rely on the event loop to signal it about the socket status changes, like c-ares or libssh2. Using PollHandle for any other purpose is not recommended; TcpHandle, UdpHandle, etc. provide an implementation that is faster and more scalable than what can be achieved with PollHandle, especially on Windows.
It is possible that poll handles occasionally signal that a file descriptor is readable or writable even when it isn’t. The user should therefore always be prepared to handle EAGAIN or equivalent when it attempts to read from or write to the fd.
It is not okay to have multiple active poll handles for the same socket, this can cause libuv to busyloop or otherwise malfunction.
The user should not close a file descriptor while it is being polled by an active poll handle. This can cause the handle to report an error, but it might also start polling another socket. However the fd can be safely closed immediately after a call to stop() or close().
Note: On windows only sockets can be polled with poll handles. On Unix any file descriptor that would be accepted by poll(2) can be used.
Note: On AIX, watching for disconnection is not supported.
Implementations§
source§impl PollHandle
impl PollHandle
sourcepub fn new(loop: &Loop, fd: File) -> Result<PollHandle>
pub fn new(loop: &Loop, fd: File) -> Result<PollHandle>
Create and initialize a new poll handle using a file descriptor
sourcepub fn new_socket(loop: &Loop, socket: Socket) -> Result<PollHandle>
pub fn new_socket(loop: &Loop, socket: Socket) -> Result<PollHandle>
Create and initialize a new poll handle using a socket descriptor. On Unix this is identical to new(). On windows it takes a SOCKET handle.
sourcepub fn start<CB: Into<PollCB<'static>>>(
&mut self,
events: PollEvents,
cb: CB
) -> Result<()>
pub fn start<CB: Into<PollCB<'static>>>( &mut self, events: PollEvents, cb: CB ) -> Result<()>
Starts polling the file descriptor. events is a bitmask made up of READABLE, WRITABLE, PRIORITIZED and DISCONNECT. As soon as an event is detected the callback will be called with status set to 0, and the detected events set on the events field.
The PRIORITIZED event is used to watch for sysfs interrupts or TCP out-of-band messages.
The DISCONNECT event is optional in the sense that it may not be reported and the user is free to ignore it, but it can help optimize the shutdown path because an extra read or write call might be avoided.
If an error happens while polling, status will be a libuv::Error. The user should not close the socket while the handle is active. If the user does that anyway, the callback may be called reporting an error status, but this is not guaranteed. If status == EBADF polling is discontinued for the file handle and no further events will be reported. The user should then call close() on the handle.
Note: Calling start() on a handle that is already active is fine. Doing so will update the events mask that is being watched for.
Note: Though DISCONNECT can be set, it is unsupported on AIX and as such will not be set on the events field in the callback.
Note: If one of the events READABLE or WRITABLE are set, the callback will be called again, as long as the given fd/socket remains readable or writable accordingly. Particularly in each of the following scenarios:
- The callback has been called because the socket became readable/writable and the callback did not conduct a read/write on this socket at all.
- The callback committed a read on the socket, and has not read all the available data (when READABLE is set).
- The callback committed a write on the socket, but it remained writable afterwards (when WRITABLE is set).
- The socket has already became readable/writable before calling start() on a poll handle associated with this socket, and since then the state of the socket did not changed.
In all of the above listed scenarios, the socket remains readable or writable and hence the callback will be called again (depending on the events set in the bitmask). This behaviour is known as level triggering.
Trait Implementations§
source§impl Clone for PollHandle
impl Clone for PollHandle
source§fn clone(&self) -> PollHandle
fn clone(&self) -> PollHandle
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more