ISSUE-161: Enable progress discovery instead of returning fixed array of services
Enable progress discovery instead of returning fixed array of services
- State:
- CLOSED
- Product:
- Network Service Discovery
- Raised by:
- Frederick Hirsch
- Opened on:
- 2014-05-15
- Description:
- 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?). - Related Actions Items:
- No related actions
- Related emails:
- Re: NSD spec implementation feedback (from w3c@fjhirsch.com on 2014-05-15)
- DAP-ISSUE-161: Enable progress discovery instead of returning fixed array of services [Network Service Discovery] (from sysbot+tracker@w3.org on 2014-05-15)
Related notes:
No additional notes.
Display change log
