On Sunday, 25. Februar 2007 23:16, Erik Johansson wrote: > I think the daemon should load all data from disk and create a TOwner > instance. A pointer to this instance is then handed to the protocol plugin > for it do whatever it likes with it. TOwner would have any number of > key/value pairs should this should not be a problem for the plugin. And it > can easily be saved to and loaded from disk by the daemon. In any format.
Why burden the daemon with such an ungreatful task? Why not let some plugin do
this? (Refer to my reply on a service like plugin structure.)
The costs: Just another plugin which could handle data persistance.
The benefit: The persistence solution can be exchanged. Maybe some user does
not want to store his owner data on the hard disk, but in a centralized LDAP
store or a mysql database.
With the daemon handling the persistence, this wouldn't be easy. With a plugin
it is just a matter of activation. :)
Greetings,
Stefan
--
____
/ \
/ ^ ^ \ Stefan Haun
I \/ I [EMAIL PROTECTED]
II II http://www.tuxathome.de
II II
I /\/\ I
pgphYFqiURqfe.pgp
Description: PGP signature
