Am 29.01.2014 10:23, schrieb Johannes Morgenroth:
Am 29.01.2014 09:40, schrieb Christian Raffelsberger:
By the way, I think it's reasonble in some situations to start the daemon automatically if an app that requires the daemon is started.
Let's start a discussion on that. :-)
Oh, I was afraid this was going to happen ;-)
But first, I like to explain something. The on/off state of the daemon only affects the networking behavior and if the process will stay running in background. An application can always send and receive bundles, even if the daemon is switched off. Since the network behavior effects the users battery and the background process reduces the memory consumption, I prefer to leave the authority to switch the daemon on/off to the user alone.
Now I am curious to know which situation you consider as reasonable to switch the state of the daemon in the applications.
I thought about the battery problem aswell. Thus, I said "in some situations". For instance, we have written a prototype application that can be used by fire fighters or other first responders to locate victims. One feature that we experiment with is using the bundle protocol to send collected data to the command post. One of the most important requirements is to minimize user intevention (i.e., the fire fighter just activates the device and puts it in his/her pocket). In that case it is not feasible that the fire fighter manually starts the daemon. I know that this is a rather special use case and probably in general you are right that preserving battery is more important than usability.
Best regards, Christian