DAP-ISSUE-161: Enable progress discovery instead of returning fixed array of services [Network Service Discovery]

DAP-ISSUE-161: Enable progress discovery instead of returning fixed array of services [Network Service Discovery]

http://www.w3.org/2009/dap/track/issues/161

Raised by: Frederick Hirsch
On product: Network Service Discovery

On behalf of Youenn Fablet

See http://lists.w3.org/Archives/Public/public-device-apis/2014Apr/0022.html

2.       Returning an array of services is not flexible.
Progressive discovered service return (like sending an event per granted service) seems a better choice than a fixed array of services.
This model is closer to existing discovery node.js modules.

This gives the flexibility to the user agent to send discovered services at various times:
- according the granting process (always-granted services, user-clicked-granted services...)
- according the discovery process (new service appearing).
Also, recalling the NSD API when a new service is appearing may not be that efficient, both for web app (user denied a previously agreed service, by mistake?) or for user (which service is new?).

Received on Thursday, 15 May 2014 18:59:07 UTC