...
This state machine describes the state transitions per player session in the Rialto Client.
TODO: Fix state diagram (it should render OK in another PlantUML viewer)
| PlantUML Macro | ||
|---|---|---|
| ||
@startuml
hide empty description
state All {
All --> Failure: server.failure
All --> [*]: client.stop(), server.PLAYBACK_STATE_STOPPED
state Seekable {
[*] --> Buffering: server.NETWORK_STATE_BUFFERING / server.NETWORK_STATE_BUFFERING
Buffering --> Playing: server.PLAYBACK_STATE_PLAYING
Playing --> Buffering: server.NETWORK_STATE_STALLED
Seeking --> Buffering: server.PLAYBACK_STATE_FLUSHED
Seekable --> Seeking: server.PLAYBACK_STATE_SEEKING
All --> Eos: server.PLAYBACK_STATE_EOS
}
}
@enduml |
State diagram snapshort since PlantUML not rendering correctly above:
The following table defines how various calls should be handled by Rialto client depending on the state of the player session:
...