Hello, Thanks for the quick answer!
Andrew Danforth wrote: > You could call event_init immediately after you fork in a child to get a > fresh libevent instance. Hmm. That's what I tried immediately, but it didn't work very well. I'll give it another shot. Is this supposed to work in older versions of libevent too? > If it works, your children will > inherit the parent's epoll fd but just ignore it. Not sure if that's > the behavior you'd like. Well, it's acceptable. Cleaning up everything would be nicer, of course... > libevent, and event based programming in > general, allow you to service multiple clients from the same process > quite easily. > It can do that. But borrowing code from Gaim 0.58 doesn't make it that easy. ;-) BitlBee can do everything in one process, but when serving tens of clients, it's a matter of time before some critical bug kills the program and a whole bunch of connections. We're working on stability improvements, but we're not quite there yet. Wilmer van der Gaast. -- +-------- .''`. - -- ---+ + - -- --- ---- ----- ------+ | wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org | | lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net | +--- -- - ` ---------------+ +------ ----- ---- --- -- - +
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkey.org/mailman/listinfo/libevent-users
