W3C home > Mailing lists > Public > public-device-apis@w3.org > October 2013

[discovery-api][ISSUE-130][ACTION-654] wildcard api

From: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
Date: Thu, 24 Oct 2013 17:48:38 +0200
Message-ID: <52694156.4070804@telecom-paristech.fr>
To: Device APIs Working Group <public-device-apis@w3.org>
Dear all,

Here is proposed text for ISSUE-130, as part of ACTION-654:
Propose text for network service discovery to define wildcard api and 
feature detection

This is modelled against the latest text for getNetworkServices.
I am very flexible for the name of that function, as well as other 
aspects of the proposal.

====================

promise = window.navigator.discover(fragment)

Immediately returns a new Promise object and then the user is prompted 
to select discovered network services that have advertised support for a 
service whose type contains the given fragment.
If the user accepts, the promise object is resolved, with a 
NetworkServices object as its argument.
If the user declines, or an error occurs, the promise object is rejected.

The implementation of the discover function is optional, as it requires 
the user agent to monitor the network for device and service 
announcements. A web application may test the existence of the discover 
function by testing whether window.navigator.discover is a function.

When the discover(fragment) method is called, the user agent must run 
the following steps:

1. Let Network Service Promise be a new Promise object.
2. Let Network Service Promise's Resolver be the default resolver of 
Network Service Promise.
3. Return Network Service Promise, and run the remaining steps 
asynchronously.
4. Process: Let services found be an empty array.
5. For each available service in the list of available service records 
run the following steps:
5.1 If available service's type attribute contains the fragment argument 
then let matched service equal the value of available service. 
Otherwise, abort the remaining sub-steps and continue above at the next
available service.
5.2 same as 9.2 of getNetworkServices
6+. same as 10+. of getNetworkServices

====================

Best regards
JC
-- 
TÚlÚcom ParisTech <http://www.telecom-paristech.fr> 	*Jean-Claude
DUFOURD <http://jcdufourd.wp.mines-telecom.fr>*
Directeur d'Útudes
TÚl. : +33 1 45 81 77 33 	37-39 rue Dareau
75014 Paris, France

Site web <http://www.telecom-paristech.fr>Twitter
<https://twitter.com/TelecomPTech>Facebook
<https://www.facebook.com/TelecomParisTech>Google+
<https://plus.google.com/111525064771175271294>Blog
<http://jcdufourd.wp.mines-telecom.fr>
Received on Thursday, 24 October 2013 15:49:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:01 UTC