ISSUE-6: Use Case: Document as a Service Provider
UC Service Provider
Use Case: Document as a Service Provider
- State:
- CLOSED
- Product:
- HOME_NETWORK_TF
- Raised by:
- Jean-Claude Dufourd
- Opened on:
- 2011-04-21
- Description:
- http://www.w3.org/2011/webtv/wiki/HNTF/Home_Network_TF_Discussions/ServiceProvider
formerly a part of ISSUE-2 - Related Actions Items:
ACTION-26 on Jean-Claude Dufourd to Clarify in the text of ISSUE-6 that the document is acting as a device and split in more atomic use cases - due 2011-05-10, closed- Related emails:
- Re: [HOME_NETWORK_TF] Issue and Requirements Summary (from giuseppep@opera.com on 2011-08-01)
- [HOME_NETWORK_TF] Issue and Requirements Summary (from r.berkoff@sisa.samsung.com on 2011-07-26)
- Re: [HOME_NETWORK_TF] improved implementation alternative (from jean-claude.dufourd@telecom-paristech.fr on 2011-05-23)
- Re: [HOME_NETWORK_TF] improved implementation alternative (from giuseppep@opera.com on 2011-05-23)
- [HOME_NETWORK_TF] Finished ACTION-26 (from jean-claude.dufourd@telecom-paristech.fr on 2011-05-05)
- webtv-ISSUE-14 (UCDiscoverService): Document Discovering a Service [HOME_NETWORK_TF] (from sysbot+tracker@w3.org on 2011-05-05)
- webtv-ISSUE-13 (UCRespondToRequests): Document Responding to Requests [HOME_NETWORK_TF] (from sysbot+tracker@w3.org on 2011-05-05)
- webtv-ISSUE-12 (UCExposeService): Document Exposing a Service [HOME_NETWORK_TF] (from sysbot+tracker@w3.org on 2011-05-04)
- [HOME_NETWORK_TF] Minutes of TF call 2011-05-03 (from fd@w3.org on 2011-05-03)
- RE: webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF] (from r.berkoff@sisa.samsung.com on 2011-04-26)
- Re: webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF] (from jean-claude.dufourd@telecom-paristech.fr on 2011-04-26)
- Re: webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF] (from r.berkoff@sisa.samsung.com on 2011-04-26)
- webtv-ISSUE-6 (UC Service Provider): Use Case: Document as a Service Provider [HOME_NETWORK_TF] (from sysbot+tracker@w3.org on 2011-04-21)
Related notes:
[Samsung] UPnP does not allow unencapsulated services or casual access to SSDP so a UPnP device wrapper would need to be provided. At that point the proffered UPnP device would become discoverable and could offer UPnP services. This assumes the UA supported the necessary UPnP stack functions (GENA, SSDP, SOAP, HTTP)and the page could access these functions. The question is loading a document into a UA that turns it into a UPnP device beneficial? Note: this could present significant security concerns. Also the question of the lifetime of the page and the ability page to establish itself as a background process become relevant.
Russell Berkoff, 22 Apr 2011, 07:08:06Display change log
