with bufferevent_enable() and bufferevent_disable().
When reading is enabled, the bufferevent will try to read from the
- file descriptor onto its input buffer, and and call the read callback.
+ file descriptor onto its input buffer, and call the read callback.
When writing is enabled, the bufferevent will try to write data onto its
- file descriptor when writing is enabled, and call the write callback
- when the output buffer is sufficiently drained.
+ file descriptor when the output buffer has enough data, and call the write
+ callback when the output buffer is sufficiently drained.
Bufferevents come in several flavors, including:
By default, this loop will run the event base until either there are no more
added events, or until something calls event_base_loopbreak() or
- evenet_base_loopexit(). You can override this behavior with the 'flags'
+ event_base_loopexit(). You can override this behavior with the 'flags'
argument.
@param eb the event_base structure returned by event_base_new() or