kc3-lang/libevent/include
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
2888facc | 2011-07-04 23:02:11 | Revise the event/evbuffer/bufferevent doxygen for clarity and accuracy | |
|
9556a7d1 | 2011-05-02 23:22:09 | Add missing words to EVLOOP_NONBLOCK documentation | |
|
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. | |
 |
5dc56628 | 2011-02-24 12:30:40 | Workaround libevent bug https://sourceforge.net/tracker/index.php?func=detail&aid=3078187&group_id=50884&atid=461324 The problem is that bufferevent_disable() doesn't disable EV_WRITE when 'connecting' flag is set. However from evhttp_connection_reset() we want to disable EV_WRITE for sure (we are closing the socket next). So we add bufferevent_disable_hard(), which acts like bufferevent_disable(), but resets 'connecting' flag before the call to the actual handler. TODO: bufferevent_disable_hard() shouldn't be public, remove it from event2/bufferevent.h. | |
 |
b5ab9555 | 2011-02-25 10:35:12 | Make --no-libevent-install apply to headers too | |
|
5dc200b7 | 2011-02-22 18:53:55 | Merge branch '20_uri_nonconformant' into patches-2.0 | |
|
f95bafb6 | 2011-02-22 00:34:49 | Be explicit about how long event loops run in event.h documentation | |
|
f6659246 | 2011-02-15 11:33:40 | Correct evhttp_del_accept_socket documentation on whether socket is closed Thanks to Constantine Verutin for pointing this out. | |
|
926f8165 | 2011-02-13 00:54:21 | Clarify event_set_mem_functions doc | |
|
95060b54 | 2011-02-13 00:41:22 | Make URI parser able to tolerate nonconformant URIs. If the EVHTTP_URI_NONCONFORMANT flag is passed in (which it is when parsing URIs we get over the wire), then we relax our checks a lot. Specifically, we do nothing to check for correct characters in the path, query, and fragment parts of such a URI. We could do much more here: we could relax our hostname requirements, deal with spaces differently/better, trap some errors but not others, etc. But this should solve the worst user-agent compatibility issues for now; the other issues can wait for a later release. |