Doug Turner wrote: > Christopher Blizzard wrote: > >> Doug Turner wrote: >> >>> Christopher Blizzard wrote: >>> >>>> Doug Turner wrote: >>>> >>>>> >>>>> Exactly. Shared files could exist anywhere and come from any >>>>> source (not just an ldap backend). >>>>> >>>>> >>>> >>>> Shared files or shared structured data? >>>> >>>> Take prefs for example. You could save the prefs as a blob and >>>> upload them to a web server, or you could just update whatever has >>>> changed to some kind of structured data store. >>>> >>>> --Chris >>>> >>> shared files; sharing anything more grandular probably will be a >>> huge performance hit. >>> >> >> huh? It doesn't have to be. In fact it can be a performance win. I >> wasn't talking about actually saving and flushing the prefs at each >> change. > > > oh. I misunderstood. > >> Imagine if you updated 2 prefs out of 100 and then only had to sync >> the 2 prefs instead of all 100 at shutdown (or once every 5 minutes.) >> That would be a performance gain. > > > I am sure that we could be smart about when and how we write preferences > and shared data back to a "roaming" server.
Right; we could even just journal changes immediately to disk and write them back to the roaming server in the background (either asynchronously or on a different thread). Dan
