[EMAIL PROTECTED] (Linas Vepstas) writes:
> It would be seriously cool if gconf was distributed, so that, e.g.
> when machine 2 shows up on net, its gconf would sync with that from
> machine1. After sync machine1 could be shut down, or whatever ...
> machines could come & go, join the party & leave... the data would
> persist.
Well, perhaps if data were just stored in $HOME we wouldn't need
a daemon to 'cache' it. Or I suppose it could be a write-through
cache... But at that point why not just provide a common app library
to read a set of dotfiles in $HOME?
> As a side note, corba does have this 'service discovery' feature, this
> thing where you can ask "who holds the gnucash config data" and there
> would come this response "oh, machine 10.0.0.1 holds it", so the user
> does not need to specify any explicit machine name for the service.
> I have no idea if gconf uses this, it would be cool if it did.
I dont know.. Corba just seems so overkill for configuration
parameters, especially when a simple set of dotfiles would suffice!
> --linas
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
