Lines Matching refs:handle

153 When libev catches an operating system error it cannot handle (for example
360 The default loop is the only loop that can handle C<ev_child> watchers,
432 otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
454 want to handle signals only in specific threads and want to avoid libev
788 would be best to handle timeouts as if no time had actually passed while
833 A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
836 iteration of the loop. This is sometimes useful to poll and handle new
840 necessary) and will handle those and any already outstanding ones. It
960 The idea is that sometimes your program runs just fast enough to handle
967 time collecting I/O events, so you can handle more events per iteration,
1493 C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle
1506 For example, to emulate how many other event libraries handle priorities,
1515 miserably under the type of load it was designed to handle. In that case,
1531      // are not yet ready to handle it.
1534      // start the idle watcher to handle the actual event.
1715 One of the easiest ways to handle this situation is to just ignore it
1718 event-based way to handle this situation, so it's the best one can do.
1720 A better way to handle the situation is to log any errors other than
1733 The last way to handle it is to simply log the error and C<exit>, as
1769      .. read from stdin here (or from w->fd) and handle any I/O errors
1805 What follows are some ways to handle this problem, from obvious and
2969 example, if you want to handle a large number of connections fairly, you
4229 of the libev API and adds file handle abstractions, asynchronous DNS and
4547 C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise,
4559 =item EV_WIN32_HANDLE_TO_FD(handle)
4563 their own fd to handle mapping, overwriting this function makes it easier
4568 If programs implement their own fd to handle mapping on win32, then this
4571 the underlying OS handle.
5326 The most portable way to handle signals is to block signals in all threads