The application can be divided into three performance spaces — mediaplayer(MP), proxy(PRX) and exterior(EXT) — which have the task to perform and respond to requests. The MP is the source of commands given by the user.
Figure 1: General Architecture
As shown in Figure 1, the MP performs an, not persistent, HTTP messaging session and therefore, it is necessary to open a new connection for each request. This setting allows to simplify the application code and it doesn´t created a big restriction since communications are performed over the loopback interface of the device.
The video player used on the Android platform, performs a priori an resource management, obtaining data only when necessary and without draining the device memory. However, it should be noted that trought the use and experience of the same, noticed there is some repetition in the requests made. Thus, it was installed in PRX, a cache memory, to improve the response.
The PRX function is to respond to requests from the MP with obtained remote data bytes. Thus, the basic function of this area of execution is managing and coordinating the data collection. In the next sections will describe the various policies available in the application.
