Re: [Libbt-devel] role of libevent
Brought to you by:
ksmathers
From: Alien <ali...@us...> - 2005-02-10 16:15:19
|
Op donderdag 10 februari 2005 17:03, schreef Emil Sit: > On Thu, 10 February 2005 at 16:45 (+0100), Peter Stuge wrote: > > libraries. I can certainly live with select() in libbt as for > > performance, I think it will be good enough. But, on the other hand, > > Performance is not the issue. The hard problem is how to isolate > event-handling code from the details of the library/application so > that you have a clean and maintainable program. Much of the work > that I did was to create clean abstractions. > > The hard part about making libbt a library is in allowing the I/O > handling to integrate with the program that it is being linked into. > If your application uses X, how do you integrate X event loop > and select/poll/libevent-abstracted I/O handling? > > giFT seems to have the right idea by isolating the I/O into > a separate process and communicating using RPCs with front-end > applications. well, that was more or less my idea about splitting btget and libbt, and th= at=20 is what i am working on now. i have not looked at this more, but the simplest thing to split it up is to= =20 provide a init, update and free function to frontends, with the idea that t= he=20 update function has to be called in some kind of loop, until it returns 0 o= r=20 something similar... maybe i should look into giFT and see what they have as a system any other idea's are welcome =2D-=20 Alien is my name and head-biting is my game. |