<Cloud-Log starting at 2012.02> [emulated from Captain’s Log on Starship Enterprise]
If only the video player of the yester-years talked to a remote server, we could see how the press of a play button requested the content to be streamed back. Today the “video” player on the client’s browser can emulate that effect through a GET command.
Since now the things got to get more specialized, the fetch/view builder function on the streaming server need to be sub-divided amongst various view-helper functions and clients (web browsers). Some helpers could build the basic “scene” background; some could fill-in the already saved responses in the field columns of the resource representation.
The record button on the video player, had more specialized functions including creating, deleting, and updating all rolled into one, a function which just bluntly over-wrote everything (at the current position)! For business applications running on the player, we must be more explicit. So we will have at least two buttons on our app player – POST, DELETE (if not three that is – PUT) replacing the Record’s red dot button.
The stop button now must function as a logout button, releasing all the client caches and memory (a good citizen’s charter)!
The most important achievement of a video player’s interface was its simplicity stemming probably from the sequential access (though was implemented with the help of a few more buttons – Forward and Rewind). The app player too will need to bring the same for a randomly accessed data.
More on this in the following post…
Related articles
- Where is my Application “Player”? (vikasjee.wordpress.com)