On 17.10.2010 23:12, David Lanzendörfer wrote: > For performance optimation I would suggest, that we give kdbus a shot.
Maybe, but than should not be our primary goal. > Downloadmanager, packagemanager, etc. should be communicating > with relative system services. > e.g. networking shall not be shut downed, as long a download is in progress. > and fsosyncd shall be notified by networkmanager. We already have resources in FSO so we should define dependencies between the resources. So if someone wants to shutdown network and network as active dependencies like the downloadmanager it should not be shutdown until the downloadmanage finishes. But we should even define priorities. So if the network manage recieves a shutdown command with a high priority it should not take care of its dependencies if they are not finished and should shutdown immediately. >> As the application interface implementation is available as xml we >> should even provide a lib called libfso-app which implements all the >> interface in vala or your favourite language so you can easily use it. > Or even visual code generators. (Flowdiagram -> code) Hehe, would be a nice feature. >> So far from my side. I have some more ideas, but will need some time to >> write them down. > Well done! > Keep on working like that. Thats great! ^^ > Thanks :) _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
