[discovery-api] loophole in current getNetworkServices flow

It seems to me there is a loophole in the current getNetworkServices flow.

After a call to getNetworkServices, the successCallback is called, and a 
NetworkServices object is provided.
Then I can set onserviceavailable of that object to a suitable Event 
Handler.
What if a service becomes available between the time the NetworkServices 
is created and the time I set onserviceavailable ?
The underlying implementation has no way to know whether I am not 
interested in new services or if I did not have time to set the handler yet.

Best regards
JC

-- 
JC Dufourd
Directeur d'Etudes/Professor
Groupe Multimedia/Multimedia Group
Traitement du Signal et Images/Signal and Image Processing
Telecom ParisTech, 37-39 rue Dareau, 75014 Paris, France
Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144

Received on Thursday, 7 February 2013 16:58:52 UTC