Re: [reSIProcate-users] Resiprocate design
To be honest, I took a close look at libevent a while ago and did a
bunch of experiments with it and concluded that it was not the right
library to solve this problem. I can't remember the exact problems I
ran into but when I took a look at the source code for libevent there
was a lot of stuff missing.
I think the asio library is much better and accomplishes similar goals
to libevent - in a much better implementation - that has been peer
reviewed by the boost community. asio has been accepted by boost but
is not yet part of the latest release.
See http://asio.sourceforge.net/
Jason
On Jan 31, 2008 10:45 AM, Ryan Kereliuk <ryker@xxxxxxxxx> wrote:
> I just wanted to highlight this point for people experiencing performance
> problems. It is not too difficult to shoehorn epoll into the open source
> implementation but the right approach would be to integrate with libevent.
>
> Thanks,
> -Ryan
>
> On 2008-01-31 at 09h41, Jason Fischl wrote:
> >
> > - If you are doing lots of TCP connections, the current open source
> > implementation is not efficient at all and will not scale without
> > design changes.
>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>