I’m looking at: http://www.wangafu.net/~nickm/libevent-book/Ref6a_advanced_bufferevents.html
where it says: "Currently the only workaround is to do lazy SSL shutdowns manually. While this breaks the TLS RFC, it will make sure that sessions will stay in cache once closed. The following code implements this workaround.” Is this still the case? I was hoping that libevent had gotten updated and the book was lagging behind... Also, are there any good examples of error handling for both a TCP listener and an SSL listener? Because there seem to be a lot more failure modes than a simple UDP unbound socket. Thanks, -Philip *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe libevent-users in the body.
