3rd Party Extension Hosts May Override Dashclock Service Binding

What steps will reproduce the problem?
1. Create a host cloning Dashclock with the purpose of reading Dashclock 
extensions data.

What is the expected output? What do you see instead?

I would expect hosts to be able to bind to extensions without impeding 
Dashclock from getting updates and viceversa. Currently they override Dashclock 
update mechanism, leaving dashclock in the dark.

What version of the product are you using?

latest 1.5

Please provide any additional information below.

In the latest API there is a World Readable flag for extensions to implement 
when they want to expose their data to other consumers beside Dashclock. The 
DashClockService exposes a binding interface to fetch visible extension data. 
Currently when binding to extensions directly as Dashclock does without going 
through this interface (commented as being private) extensions hold an instance 
to the host so any other host that is not dashclock overrides this mHost 
instance by placing it's own as the new host and Dashclock stops receiving 
updates. 

What is the recommended way to consume Dashclock extensions data if any? What 
is the world-readable property for? Is there a way for third party consumers 
that act as extensions hosts to play nicely with Dashclock so everyone receives 
updates accordingly?

thanks!

Original issue reported on code.google.com by raulr...@gmail.com on 1 Mar 2014 at 2:02

AlexChumakou / dashclock

3rd Party Extension Hosts May Override Dashclock Service Binding #741