W3C home > Mailing lists > Public > public-web-and-tv@w3.org > July 2016

[Cloud Browser] Session Use-Cases

From: Eugen Osiptschuk <eugen.osiptschuk@campus.tu-berlin.de>
Date: Wed, 6 Jul 2016 11:55:43 +0200
To: <public-web-and-tv@w3.org>
CC: Alexandra Mikityuk <alex@sec.t-labs.tu-berlin.de>
Message-ID: <1e6193ae72224d9db2dc4e029159c8b7@EX-MBX-02.tubit.win.tu-berlin.de>
Hey guys,
I have been working on some session use-cases in the last couple of 
weeks and would like to present you some of my ideas and also some open 

The idea is to associate the UI stream and a specific session id, so 
that for each session there will be one UI stream but possibly many 
control channels. This allows also the cloud browser run-time 
environment to save specific resources associated with a session id. 
Maybe it will also help in load balancing the traffic. Underneath you 
can find some use-cases i have written, but they are still in draft 
version and open for discussion.

UC-Session-1: Cloud Browser client creates a session with the Cloud Browser
     For each session there will be one UI stream and one or more 
control channels. Also the Cloud Browser environment can store resources 
associated to the session.

     The Cloud Browser client ...
     1. Connects to the Cloud Browser rte
     2. Authenticates itself
     3. If authentication was successful the Cloud Browser rte responds 
with a session ID
     * Cloud Browser Client
     * Cloud Browser rte
     * The authentication method is not specified.
     This could be implemented by a HTTP GET request to a specific URL.

This use-case provides some questions:
     1. Should the cloud browser client directly connect to the cloud 
browser run-time environment? Or maybe to a vendor website and this 
website will create a session?
     2. Should there be one session for each user? Or more?
     3. Should the authentication be also specified?
     4. If for example a set-top box starts up, how should it create the 
session id?

UC-Session-2: Cloud Browser client logs out from session
     The Cloud Browser client sends the log out message through the 
control channel with the appropriate session id.

     The Cloud Browser rte can now safely assume that the client logged 
out and free any specific resources to the session.
     * Cloud Browser Client
     * Cloud Browser rte
     There is at the moment no specific message format used for the 
communication within the control channel.

Questions regarding this use-case:
     1. Should the cloud browser client be able to destroy a session, 
maybe through a RPC or special message? Or should this be possible 
through a vendor website?

Some questions open in general:
     1. What about other session management operations, like the 
listening of open session? Even necessary?

Eugen Osiptschuk
Received on Wednesday, 6 July 2016 09:57:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:57:31 UTC