Solid and Akonadi? (was: Re: Discontinuing kcmwifi for wpa_supplicant, what about knetworkmanager?)
carpdjih at mailbox.tu-berlin.de
Wed Apr 5 13:28:26 BST 2006
On Monday 03 April 2006 14:22, Will Stephenson wrote:
> The Akonadi daemon acts as a local cache; it's always available to Kontact
> etc. The parts that talk to remote servers will be separate processes
> again, so these need to be suspend- or cleanly killable in the case of
> impending network disconnection. The centre of Solid/network status
> integration will therefore be in the scheduler, this will handle status
> changes from Solid and user requests to 'Work On/Offline'.
I'm afraid simply killing or suspending processes that deal with remote
resources might not be sufficient. There needs to be a local persistent
storage facility as well.
Imagine you work with documents, that are associated with a remote resource
and your network is down (not uncommon, when e.g. working in a train). Now
your battery runs out and you need to shut down your laptop. You want to have
all your data stored locally until you next have a network connection again.
Then you want to be asked whether your data should be uploaded to the remote
Also see https://bugs.kde.org/show_bug.cgi?id=85897
More information about the kde-core-devel