From: <sj...@sp...> - 2007-03-18 13:39:32
|
On Fri, Mar 16, 2007 at 08:22:38PM +0100, Kristoffer Lundén wrote: > I was a bit unclear. Actually I don't have a mainloop in that sense, > but all messages are sent and received in their own lightweight > thread, which handles sync and async messages and signals etc > seamlessly. The end user never sees anythig about this, but only makes > the requests. From what I can tell, if you start a Glib or any other > mainloop, things will just keep on working as they should. Could you be a little more specific about this ? Maybe some (pseudo)-code examples ? The approach sounds a little bit problamatic to me. But then again I really dislike threads being spawned behind the users back, but maybe you can prove me wrong here :) > I assume there's extra benefits if you have a GLib mainloop anyways to > be able to use those signals natively and stuff, but I think that > could easily be solved by importing an extra lib when it's available I > think. I'm not actually sure what people want here, but I am > interested to know. :) > And personally I think that GLib can be all the de facto standard it > wants, but it would be horrible to have that as anything but an > optional dependency. :) I'd never ask to make it a mandatory dependency, that would be really bad. Sjoerd -- The following statement is not true. The previous statement is true. |