bufferevent-internal.h

Branch :

Log

Commit	Date	Message
50ec59f4	2010-04-28 15:16:32	Remove redundant checks for lock!=NULL before calling EVLOCK_LOCK The EVLOCK_LOCK and EVLOCK_UNLOCK macros already check to make sure that the lock is present before messing with it, so there's no point in checking the lock before calling them. A good compiler should be able to simplify code like if (lock) { if (lock) acquire(lock); } , but why count on it?
fb366c1d	2010-03-21 13:16:31	Functions to track the total bytes sent over a rate limit group.
f1bc125e	2010-03-12 23:00:49	Improve robustness for refcounting Document that we do intend to double-decref underlying bufferevents under some circumstances. Check to make sure that we don't decref past 0.
2c2618d8	2010-03-05 13:00:15	more whitespace normalization
17efc1cd	2010-03-04 01:25:51	Update all our copyright notices to say "2010"
7bc48bfd	2010-02-27 18:59:06	deal with connect() failing immediately
d3288293	2010-02-20 18:44:35	Provide consistent, tested semantics for bufferevent timeouts The different bufferevent implementations had different behavior for their timeouts. Some of them kept re-triggering the timeouts indefinitely; some disabled the event immediately the first time a timeout triggered. Some of them made the timeouts only count when the bufferevent was actively trying to read or write; some did not. The new behavior is modeled after old socket bufferevents, since they were here first and their behavior is relatively sane. Basically, each timeout disables the bufferevent's corresponding read or write operation when it fires. Timeouts are stopped whenever we suspend writing or reading, and reset whenever we unsuspend writing or reading. Calling bufferevent_enable resets a timeout, as does changing the timeout value.
4b37e6a5	2010-02-23 00:39:02	Merge remote branch 'github/split_free_from_decref'
b2fbeb3f	2010-02-22 15:38:23	Make bufferevent_free() clear all callbacks immediately. This should end the family of bugs where we call bufferevent_free() while a pending callback is holding a reference on the bufferevent, and the callback tries to invoke the user callbacks before it releases its own final reference. This means that bufferevent_decref() is now a separate function from bufferevent_free().
db08f640	2010-02-20 12:55:59	Suspend read/write on bufferevents during hostname lookup When we're doing a lookup in preparation for doing a connect, we might have an unconnected socket on hand, and mustn't actually do any reading or writing with it.