On Thu, 22 Feb 2007 07:49:42 +0100, Jon Keating <[EMAIL PROTECTED]>
wrote:
Perhaps Erik can chime in? I agree, it would be nice to allow the
plugins to be basically the same. With the code in erijo-dev, it
appears to be that way now. But anyways, yes, I agree with you about
this.
I discussed this briefly with Erik on IRC a couple of days ago and he
seemed to like the idea. But I would also like to hear his comments on
this as I described it a bit more detailed here on the mailing list than I
did on irc.
Of course a loaded plugin will always result in the daemon holding some
information about it. What I mean here is that there will be no threads,
event handlers, sockets, etc active in an unused protocol plugin, only
the
bare minimum required to actually have the plugin loaded.
So in otherwords, don't run StartPlugin (or whatever it will be
called)...
As the protocol plugins would not be any different from ordinary plugins
at the plugin level they would still be started.
Some plugin code must be executed to actually register the protocol(s).
Besides, the plugin could need to initialize some stuff or do more than
just provide a protocol.
Whether a plugin that doesn't need to keep running should just return
immediatly or do nothing and sleep is a later question for the API.
/Anders
