kc3-lang/libevent
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
ac9f2adb | 2011-08-31 00:23:20 | Credit new contributors for 2.0.14-stable | |
|
da90a9be | 2011-08-30 22:35:51 | Pick a release date for the changelog | |
|
85976ddf | 2011-08-30 22:28:02 | Bump version to 2.0.14-stable | |
 |
54f7e61b | 2011-08-29 23:39:26 | clear read watermark on underlying bufferevent when creating filtering bev to fix potentially failing fragmented ssl handshakes | |
|
6476d92d | 2011-08-29 13:40:03 | Checkpoint changelog entries for 2.0.14-stable | |
|
e6af35d7 | 2011-08-24 21:39:28 | Correctly terminate IO on an async bufferevent on bufferevent_free | |
|
0ff2c5a9 | 2011-08-24 18:42:12 | Have test-ratelim.c support IOCP | |
|
a98da7bf | 2011-08-24 18:41:35 | Make IOCP rate-limiting group support stricter and less surprising. Previously, we wouldn't decrement read/write buckets because of IOCP reads and writes until those reads and writes were complete. That's not so bad on the per-connection front. But for group limits, the old approach makes us launch a huge amount of reads and writes whenever the group limit becomes positive, and then decrement the limit to a hugely negative number as they complete. With this patch, we decrement our read buckets whenever we launch an IOCP read or write, based on the maximum that tried to read or write. Later, when the operations finish, we re-increment the bucket based on the portion of the request that couldn't finish. | |
|
c75341b0 | 2011-08-24 18:42:00 | Support negative arguments to _bufferevent_decrement_(read/write)_buckets() | |
|
2f51dc03 | 2011-08-28 14:03:10 | Cleanup on 7c11e51e1ab: fix strtol usage |