W3C home > Mailing lists > Public > public-xg-htmlspeech@w3.org > December 2010

RE: "Protocol" requirement - Session

From: Robert Brown <Robert.Brown@microsoft.com>
Date: Tue, 14 Dec 2010 00:48:09 +0000
To: "Young, Milan" <Milan.Young@nuance.com>, Bjorn Bringert <bringert@google.com>
CC: "public-xg-htmlspeech@w3.org" <public-xg-htmlspeech@w3.org>
Message-ID: <113BCF28740AF44989BE7D3F84AE18DD197E5614@TK5EX14MBXC114.redmond.corp.microsoft.com>
I'm fuzzy on what "session" might mean.  In an IVR app it's kinda obvious -usually the duration of the call, or perhaps of a particular service request that spans calls.

But in the public web, it's unclear.  For example...

1:
I open a web site in my browser and it's speech enabled.  My "session" exists for the entire duration of me using that site.  I close the browser and reopen it next week - same user, same device - and I'm still in the same session, right?

2:
I open two different sites on the same device.  Both sites happen to use the same speech service at the back end.  They're different sites, so they're different sessions, right?  The back end is accumulating acoustic adaptation data for the user across both sessions, but contextual data is being kept separate.

-----Original Message-----
From: public-xg-htmlspeech-request@w3.org [mailto:public-xg-htmlspeech-request@w3.org] On Behalf Of Young, Milan
Sent: Monday, December 13, 2010 11:05 AM
To: Bjorn Bringert
Cc: public-xg-htmlspeech@w3.org
Subject: RE: "Protocol" requirement - Session

Session doesn't make a lot of sense to me unless there is a start and a stop.  So if you disagree on this point, we have more to discuss.

Regarding possible implementation, cookies can be unset.

 
-----Original Message-----
From: Bjorn Bringert [mailto:bringert@google.com]
Sent: Monday, December 13, 2010 2:07 AM
To: Young, Milan
Cc: public-xg-htmlspeech@w3.org
Subject: Re: "Protocol" requirement - Session

This seems reasonable to me, as long as it doesn't imply that there is a requirement for web apps or UAs to close the sessions. HTTP cookies does not have such a mechanism.

/Bjorn

On Fri, Dec 10, 2010 at 7:44 PM, Young, Milan <Milan.Young@nuance.com> wrote:
> Summary - Web application and speech services must have a means of 
> binding session information to communications.
>
>
>
> Description - This requirement applies to both local and remote services.
> HTTP cookies is an example of such a feature.  This requirement is 
> needed, for example, to support features like channel adaptation.
>
>



--
Bjorn Bringert
Google UK Limited, Registered Office: Belgrave House, 76 Buckingham Palace Road, London, SW1W 9TQ Registered in England Number: 3977902
Received on Tuesday, 14 December 2010 00:48:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 14 December 2010 00:48:45 GMT