Main Page/Cloud Browser TF/UseCases/control
Control
UC-Control-1: Cloud Browser Client establishes a control channel with the Cloud Browser
Extends
- Nothing.
Description
- The control channel is used to communicate the state of the Cloud Browser Client to the CLoud Browser, receive requests from the Cloud Browser.
- Possible work flow:
- Cloud Browser Client connects to the Cloud environment.
- Cloud Browser Client authenticates itself to the Cloud environment.
- If the authentication is successful, the Cloud environment connects the Cloud Browser with the client through the control channel.
- A TCP connection would be a possible implementation, or a UDP stream that satisfies the requirements.
Actors
- Cloud Browser Client
- Cloud Browser
- Cloud environment
Dependencies
- None.
Gaps
- None.
Notes
- Flaws in the work flow:
- Session management
- This use case could be mapped to all current architectural approaches.
Requirements
- The control channel MUST be
- reliable, so that no state change or instruction gets lost.
- in-order, instructions have to be executed in-order.
- duplex, both the Cloud Browser and the Cloud Browser Client communicate through this channel.
- Cloud environment needs a way to authenticate the client.
Author(s)
History
- 6-9-2016 Eugen Osiptschuk (talk) created
- 6-15-2016 Alexandra Mikityuk (talk) created
UC-Control-2: Cloud Browser sends request through control channel to the Cloud Browser Client
Extends
- Nothing.
Description
- The application running within the Cloud Browser issues an API call, this API call depends upon the partial or whole execution in the Cloud Browser Client.
- Work flow:
- Application issues API call (eg. JS API).
- Cloud Browser begins executing the API call.
- If a part or the whole call depends upon the client side execution, then send a request to the client.
- Client processes the request and sends the result back to the Cloud Browser (if necessary).
- Cloud Browser goes on with the execution of the API call.
- It would be possible to implement this through RPCs or a protocol.
Actors
- Cloud Browser Client
- Cloud Browser
Dependencies
- UC-Control-1
Gaps
- None.
Notes
- If the API call is synchronous then the request has to be synchronous too.
- This use case could be mapped to all current architectural approaches.
- List of possible requests:
- Set the Volume.
- Load an URL for playback (for double stream with local player).
- Play, pause, stop, seek currently playing media.
- Control client local tuner.
Requirements
- There MUST be a control channel.
- All communication MUST be validated, to make sure that no malicious data has been inserted.
Author(s)
History
- 6-9-2016 Eugen Osiptschuk (talk) created