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

RE: [discovery-api] how does serviceavailable function in practice

From: <Cathy.Chan@nokia.com>
Date: Tue, 12 Feb 2013 20:47:38 +0000
To: <richt@opera.com>, <public-device-apis@w3.org>
Message-ID: <A46437648ECB3D4F852B077AFF9099F51C93CB80@008-AM1MPN1-061.mgdnok.nokia.com>


> -----Original Message-----
> From: ext Rich Tibbett [mailto:richt@opera.com]
> Sent: Friday, February 08, 2013 7:23 AM
> To: public-device-apis@w3.org
> Subject: Re: [discovery-api] how does serviceavailable function in
practice
> 


***snip***

> >> See towards the end of Section 5.2 (which actually seems like an odd
> >> place for this text).
> 
> Perhaps we should move this to the bottom of Section 5. Any other
> suggestions?
Yes that's a good place to move it to. It actually fits nicely with the
definition of the onserviceavailable and onserviceunavailable events. I
would even consider
s/A user agent can inform a web page when the state of networked services
matching the requested valid service type change./ A user agent can inform a
web page when the state of networked services matching the requested valid
service type change using these events./

- Cathy.

> 
> >> [[Services available within the local network can connect and
> >> disconnect at different times during the execution of a web page. A
> >> user agent can inform a web page when the state of networked services
> >> matching the requested valid service type change. Web pages can use
> >> this information to enable in-page experiences for communicating the
> >> state of networked services with the ability to change the particular
> >> service or set of services the page is connected to by re-invoking
> >> the getNetworkServices() method.]]



Received on Tuesday, 12 February 2013 20:48:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:58 UTC