DESIGN discussion! Plans to change the motive of the project

[Aniketh01]

Hi,

Currently, this repo contains code which does a basic implementation of progressive streaming, which in a nutshell means that we retrieve the entire video file send it through a TCP connection to the requesting peer. Which is, of course, a redundant mechanism to follow as far as streaming is concerned as this process is subjected to stall and buffering events in case of congestion effects.

Hence it is vital to us to improve this scenario with additional features implementation that could be done which could actually get us better performance and ease of usage.

Further note, I currently, only intend to implement this project for purely research purpose where users of this project could plug and play their implementation with our code.

Both the network and video side of things could be designed as different engines which is used to drive the core principles of this project implementation. Below you can find the detailed implementation design suggestion which I would like to make:

On the streaming side:

• We should also support ABR streaming algorithms, plainly having a progressive streaming application is not good enough.
• A queueing mechanism to fill the video buffer.

On the networking side:

• Add more TCP related functionalities from the socket APIs in use.
• Add HTTP functionality on top of the current TCP code to have better design proposition.

This is just the initial plans which I would like to put forward. We could further discuss the design of the whole project within this issue.