yahor-filipchyk/mediaplayer

mediaplayer's Issues

Implement HTTP server

Implement an HTTP server that handles client requests and response to client with requested resource.
Requested resource can be:

• dynamic page
• static file
• message of any protocol that works over HTTP (e.g. XML)

Server is a kind of drive for application. It is started when application starts and it is stopped when application stops. HTTP server handles all client requests.
Server must provide an interface for web applications (something like servlets in Java). So the core logic of application will be implemented as web application that will work on created server.
Communication between client and application is following:

1. Server is binded to some port on PC where application is installed and listens to this port.
2. Client sends the request using web browser (navigates to some URL).
3. Server reads the request and parses it to the form that web application hosted on the server can understand.
4. Server passes the request object to appropriate web app (it depends on requested resource) or tries to send a static file if no needed web apps were found.
5. Web app handles the request and fills the response object that was passed to web app by server and was initialized by default values before.
6. Server waits for response object and prints it to the socket.
7. Client receives the response.

Implement Web app for home media player

Create a web application that will be hosted on the server implemented before (see appropriate task). Application should communicate with omxplayer player according to client requests. A separate process with omxplayer player should be ran by application and this process should be fully managed by web app. Each request to web app equals a single command sent to player's process.