-----Ursprüngliche Nachricht----- Von: Nick Mathewson <ni...@freehaven.net> [...] > Sounds like a big but fun project. You might want to look at > bufferevent_sock.c first; bufferevent_openssl.c has to jump through a > lot of annoying hoops because the TLS protocol has a property that > doing a read at the TLS abstraction may require a write on the > underlying stream, and vice versa. If your protocol doesn't have that > feature, you can get much, much simpler than something based on > bufferevent_openssl.c.
Thanks for the heads up. The socket-based code surely will be helpful when the implementation starts. I wrote an initial draft of how the API could look like and put it on github: https://github.com/fancycode/Libevent/blob/bufferevent_indirect/include/event2/bufferevent_indirect.h Any feedback is very welcome! Thanks and best regards, Joachim *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
