Web Intents: Hotswapping

On Tue, Nov 22, 2011 at 2:28 PM, Greg Billock <gbillock@google.com> wrote:
>>> ยง6 Hotswapping

> I'm understanding 'Hotswapping' to mean that users could select service A
> one day and service B the next. Yes, I think that's critical.

At the very least.

A pair of use cases that has been raised a lot in DAP are Sensors and Contacts.

Our pitch for them is that for a Client session one could pair with a
Sensor/Contact-Provider and make repeated requests to/from it without
triggering additional pairing requests.

> Ergonomics may mean that implementing default settings is the way to go,

right. although my view of defaults is closer to a print dialog where
your default printer is already selected and you can just click ok, or
happen to decide to change it. in this model you might not see a list
of alternatives until you decide you want to change it.

> but perhaps the spec ought to suggest the UA "should" give an easy
> way to back out of those defaults.

If there aren't session length clients and we see defaults, then yes,
this is the only should we'd need and we'd need it. If we end up with
session pairing, then we need more.

Received on Tuesday, 22 November 2011 22:24:19 UTC