bufferevent-internal.h

Branch :

Log

Commit	Date	Message
e49e2891	2012-02-10 17:29:53	Update copyright notices to 2012
3c824bd3	2011-10-24 13:18:09	Update copyright dates to 2011.
e6af35d7	2011-08-24 21:39:28	Correctly terminate IO on an async bufferevent on bufferevent_free
6d5440e8	2011-08-11 15:15:17	Fix handling of group rate limits under 64 bytes of burst The "min_share" logic, which was designed to prevent piles of extremely small writes when running up against a group rate limit, could lead to confusing behavior if you ever set a min_share less than your burst rate. If that happened, then as soon as your group rate limit was exhausted, you'd stop reading/writing, and never start again, since the amount readable/writeable would never actually hit min_share. We now cap min_share at the rate per tick. Found by George Kadianakis
c8baac90	2011-03-07 21:55:47	Followup for Tomash Brechko's http patch This patch makes bufferevent_disable_hard() non-public, and adds a comment about what it's for and why it's used.
ef5e65a4	2010-12-02 10:27:06	bufferevent-internal.h: Use the new event2/util.h header, not evutil.h
598d1336	2010-10-27 22:57:53	Try to clear up more size_t vs int/long issues.
2cbb1a16	2010-10-26 10:27:29	Make rate-limits go up to SIZE_MAX/EV_SSIZE_MAX, not just INT32_MAX Someday, when networks are far faster and people frequently want a burst value greater than 2GB per tick, this will seem very forsightful indeed. For now, it breaks ABI, but not source. Fixes bug 3092096.
ac27eb82	2010-10-08 00:59:02	Correct logic on disabling underlying bufferevents when disabling a filter Previously, whenever writing was disabled on a bufferevent_filter (or a filtering SSL bufferevent), we would stop writing on the underlying bufferevent. This would make for trouble, though, since if you implemented common patterns like "stop writing once data X has been flushed", your bufferevent filter would disable the underlying bufferevent after the data was flushed to the underlying bufferevent, but before actually having it written to the network. Now, we have filters leave their underlying bufferevents enabled for reading and writing for reading and writing immediately. They are not disabled, unless the user wants to disable them, which is now allowed. To handle the case where we want to choke reading on the underlying bufferevent because the filter no longer wants to read, we use bufferevent_suspend_read(). This is analogous to the way that we use bufferevent_suspend_write() to suspend writing on a filtering bufferevent when the underlying bufferevent's output buffer has hit its high watermark.
9c8db0f8	2010-09-23 22:45:55	Fix all warnings in the main codebase flagged by -Wsigned-compare Remember, the code int is_less_than(int a, unsigned b) { return a < b; } is buggy, since the C integer promotion rules basically turn it into int is_less_than(int a, unsigned b) { return ((unsigned)a) < b; } and we really want something closer to int is_less_than(int a, unsigned b) { return a < 0 \|\| ((unsigned)a) < b; } . Suggested by an example from Ralph Castain