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 Monday, 13 December 2010 19:05:54 UTC