bufferevent_filter.c

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
65707d7c	2011-04-11 17:40:14	add some (void) casts for unused variables All these places already have an XXX marker, so we know we need to fix them later. Let's not clutter the static analysis results with them.
7bcace2d	2010-11-22 21:02:34	Fix some irix compilation warnings spotted by Kevin Bowling
1ac5b230	2010-11-09 15:18:59	Only clear underlying callbacks when the user hasn't reset them.
fc7b1b00	2010-11-09 11:43:47	When closing a filtering bufferevent, clear callbacks on the underlying bufferevent Previously, if BEV_OPT_CLOSE_ON_FREE wasn't set on a bufferevent_filter or a filtering bufferevent_openssl, when we went to free the filtering bufferevent, we'd leave the underlying bufferevent unchanged. That's not so good, since the callbacks are set to activate stuff in the filtering bufferevent that we're about to free. Instead, set all the callbacks to NULL.
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.
ec347b92	2010-07-07 16:45:03	Move event-config.h to include/event2 This change means that all required include files are in event2, and all files not in event2/* are optional.
657d1b6d	2010-03-13 01:06:57	Set mem_offset for every bufferevent type