Re: possibly additional requirement for web intents

I think you could have:
A "start" intent which a task manager could use to let the user pick a task to run. Each task could register for "start" and when the user clicks a "start something" button, the task manager triggers the start intent and the UA lets the user pick a task.

I think task management itself would be better via WebSockets than WebIntents.

You could have a task manager intent which offers some WebSocket protocol, and if a UA receives whitelist permission from the User for your task manager to continue talking to a device, then it could probably do more or less seamless setup for future invocations. 

UI in general is left to UAs, and the general intent design is 1-1, not 1-many. You could make n requests to get access to n "task managers", and a UA as a QoI detail could elect to bubble the requests into a multiselect dialog.

That certainly won't be the initial UI implementation, although if the UC is shown to be compelling, UAs may shift to accomodate that. 

In terms of 1-many proposals, richt's proposal is friendlier to this.

At this time, WebIntents is a big enough task, so I think addressing this would be future work. 
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Thursday, 12 July 2012 16:00:15 UTC