On Wednesday 21 February 2007 05:40, Jon Keating wrote:
> > I think owners should be managed in the daemon but it will only need the
> > protocol name and owner id form the owner configuration. The rest
> > (xml-block holding any amount of parameters) is passed on to the protocol
> > implementation instance on creation.
>
> The daemon will manage the owners, mainly in the form of passing the
> data around and assigning owners to protocol plugin instances. As for
> the XML block passing around... not quite sure what you mean by that,
> just assigning by TOwnerId will allow the plugin to access the data
> from the class. Perhaps in a generic way, like the way we pass events
> around EventData::addData("messageText", "This is a test message").
> Each protocol will have different types of data to describe the owner
> (and users), so we should be as flexible as possible to make it work
> without any overly complex parts. (the current ICQOwner has *lots* of
> data fields attached to it... which doesn't do anything but waste
> memory for MSN owners).Agree. As I said elsewhere, something similar to IEvent would IMHO be nice. > What is needed is the plugin information, otherwise it will be hard to > load the plugins from a GUI. That is part of Erik's document, and it > looks like that portion will be loaded into memory for all plugins. > Erik, is that correct? Yes. The current idea is to load that information and then unload all unused libraries. The libraries would then be loaded on request (i.e. when a plugin located in that library is requested to be created). // Erik -- A nuclear war can ruin your whole day. Erik Johansson http://ejohansson.se
pgpOuZnjhGbPO.pgp
Description: PGP signature
