On Sat, Aug 22, 2009 at 3:45 PM, Zack Weinberg
<address@hidden> wrote:
I suppose I should pop back in at this point, since I started the asio
branch, and admit that I got stuck. In addition to the above
problems, asio has what is IMO a serious design flaw: its I/O channel
objects are statically typed. Since we wish to treat sockets, pipes,
and whatever-fds-0-and-1-are as interchangeable, this requires a large
hairy wrapper around all asio interfaces, which I started but got
bogged down on. I'm also not sure asio's Windows support is good
enough for us.
I've been looking at libevent instead, but it has its own problems,
e.g. not handling the creation of a network socket. It's written in
C, though, so there's no question of ABI skew, and it uses a normal
build system.
My impression is that libevent doesn't give us anything in the way of ssl help, while asio does do provide some support and uses openssl under the covers. I vaguely recall that there were/are licensing issues with using openssl directly but maybe that was back in the days of bundling various library sources or something?
Cheers,
Derek