Whenever a stream is paused or resumed on the client locally, corresponding API requests must be sent to the server in order for the stream to pause and resume the adding of assets accordingly. Otherwise listeners would miss playback of many assets when their stream was paused.
[x] implement POST streams/:id/pause/ in framework
[x] implement POST streams/:id/resume/ in framework
[x] trigger pause/ when pause button is pressed
[x] trigger resume/ when play button is pressed
[x] send pause/ immediately after stream is created since stream is created as part of app startup process rather than being created when the user proceeds to Listen and clicks Play
Whenever a stream is paused or resumed on the client locally, corresponding API requests must be sent to the server in order for the stream to pause and resume the adding of assets accordingly. Otherwise listeners would miss playback of many assets when their stream was paused.
POST streams/:id/pause/in frameworkPOST streams/:id/resume/in frameworkpause/when pause button is pressedresume/when play button is pressedpause/immediately after stream is created since stream is created as part of app startup process rather than being created when the user proceeds to Listen and clicks Play