Hi,
On Sun, May 1, 2016 at 11:55 AM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
wrote:
Am 01/05/2016 um 11:42 schrieb Dario Casalinuovo:
I don't recall everything of the discussion anyway the major problem was* Reintroduce BMediaRoster::SyncToServices, this time based onAgain, WHY? You didn't reply to my comments last time you added
local message passing rather than a global semaphore.
this, but just reverted your changes. Now you add it again.
to do it using a semaphore where this implementation is different.
It wasn't about the implementation, it was about the need for it.
Could you please enlighten me why exactly this should be necessary?
Do you expect anyone that want to know when the services are up, to
create a BLooper and start watching for this?
Who would be interested in that? And why? Do you have any particular use
case for this? I cannot think of anything useful.
What does "launch_daemon safe" mean?
Being aware that since it's introduction the services restart are
handled differently. A legacy app might call launch_media_server after
shutdown_media_server then this function allow to ask the BMediaRoster
about what's the situation.
Anybody could restart the server before, too, what's launch_daemon
specific about this? And what's the deal, anyway? Where is the difference
when you call launch_media_server() manually?
