On Monday 12 February 2007 20:55, Stefan Haun wrote: > * Firstly, the way plugins are found and loaded looks fine to me. It should > be possible to specify which directories will be scanned.
Yes, that's the idea. > Maybe the version > number which is used to check compability could be called something like > 'ABI version' because it is independent from the API version. Why not. ABI is, after all, more "correct". > * I agree that the plugin factories may remain in memory, since they would > not consume much space. Yet I would be a nice-to-have I unused modules > would be unloaded in a more mature version of licq2. Since licq is a tool > which runs everytime, it should not be too memory-consumant. > A different approach to get a list of all plugins and save memory, as > well, could be to parse only for the plugin names or only load some meta > information such as name and dependencies and then unload plugins which are > not used. A plugin can be found anytime the same way it was found on licq > startup, so there is no need to keep unused factories in memoy. Maybe we could unload unused libs after the startup is completed and all plugins that should start have started. Shouldn't be that hard to implement. > * For licq startup it would be nice to be able to specify plugins, which > have to be loaded, Check. > those which do not need to be loaded successfully Why do you want this? > and to > get some feedback which can be evaluated by some startup script, i.e. a > return value. This enables scripting actions if loading licq fails. Yes, Licq will exit with a non-zero exit value on error. // Erik -- It said Use Windows XP or better, so I installed Debian GNU/Linux. Erik Johansson http://ejohansson.se
pgpAvWMuNSAQQ.pgp
Description: PGP signature
