On Tuesday 13. February 2007 23:13, Eugene Paskevich wrote: > Particularly, is there any reason to invent a special queue in which > daemon is to send events to plugins? This queue should probably be > populated by plugins themselves upon initialization. > > The main reason here is the small glitch I observe in licq1 (a race > between osd and qt-gui) which could be solved in two different ways, one > of which is queueing... > > Looking forward eagerly to hearing your thoughts. :-)
I would prefer the classic way here: Why not implement a publisher/subscriber
structure?
I could imagine multiple queues ccovering the different aspects of messages:
protocoll messages (the ICQ/AIM/MSN/whatever messages being the reason for
developing licq at all), system messages such as plugin registrations,
configuration changes or other events. Each plugin subscribes to the queue it
is interested in.
Following this thought consequently, I end up with communication services such
as D-BUS, which is overkill for a tight coupled application, such as licq
still would be, but exactly solves the problem: Communication between loosely
coupled programs.
--
____
/ \
/ ^ ^ \ Stefan Haun
I \/ I [EMAIL PROTECTED]
II II http://www.tuxathome.de
II II
I /\/\ I
pgpmf1fBcXhaP.pgp
Description: PGP signature
