W3C home > Mailing lists > Public > public-web-intents@w3.org > January 2012

Re: Mapping WebIntents to Network Service Discovery API

From: Matt Hammond <Matt.Hammond@bbc.co.uk>
Date: Mon, 09 Jan 2012 13:49:03 -0000
To: WebIntents <public-web-intents@w3.org>
Cc: "Clarke Stevens" <C.Stevens@cablelabs.com>
Message-ID: <op.v7tkn1nuwh9xod@r44116>
On Fri, 06 Jan 2012 23:37:41 -0000, Clarke Stevens  
<C.Stevens@cablelabs.com> wrote:

> I think the mapping is fairly straightforward with one exception. For  
> some
> protocols (e.g. UPnP) it is necessary to support device-initiated events.
>
> Since I think this same requirement would exist for other frequently used
> WebIntents examples (like printing documents), I think there must be a
> common solution, but I'm having trouble finding one.

Perhaps separate "event notification" intents could implemented in a  
long-polling style? This would take advantage of an intent's ability to  
return a response.

A client would fire off this intent, then be asynchronously sent a  
response when an event occurs. The client would then need to re-fire the  
same intent to capture the next event, unless it is no longer interested  
in being notified of them.

In the context of printing, this might manifest as:

1) The client requests a PrinterStatusChangeNotification intent
2) When the printer runs out of paper, a response is returned to the  
client from this intent.
3) The client requests a PrinterStatusChangeNotification intent again
4) The client is notified when the printer changes state again
5) ...


Matt
-- 
| Matt Hammond
| Senior Research Engineer, BBC R&D, Centre House, London
| http://www.bbc.co.uk/rd/

http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
					
Received on Monday, 9 January 2012 13:49:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 January 2012 13:49:34 GMT