| GoalBit Media Server (GMS) has a GPL or Commercial license. It is developed in C++ language and its current release version is 0.7.8. |
|
 |
|
| The GMS responsabilities are: |
|
|
1. |
|
On demand content storage: All the on demand contents are stored in the GMS instances. These contents are automatically replicated to ensure the content availability, the system robustness, and a good delivery quality (having more replicas for more popular contents). The replication policy is managed by the GoalBit Suite. |
|
|
|
| 2. |
|
On demand content encoding: The GMS is able to encode the on demand contents to several encoding profiles in order to adapt the content for different technologies and devices. The avaliable encoding profiles are managed by the GoalBit Suite and the GoalBit encoding library. |
|
|
|
| 3. |
|
Live streaming adquisition: The GMS can receive the live content from different sources, like an analog signal, a streaming signal from the Internet, a stored video file, etc. It processes the signal, and generates the P2P streaming for the corresponding content. From this point of view, the GMS is seen as an origin node in the network. |
|
|
|
| 4. |
|
Live streaming transcoding: The GMS is able to take the original signal and transcode it to optimize the content for different technologies, bitrates, video resolutions, etc. |
|
|
|
| 5. |
|
Live and on demand content internal delivery: The GMS can share and replicate the contents with other GMSs in order to distribute the contents throug the entire GoalBit network, making the contents available from different nodes, and balancing the end-users distribution. |
|
|
|
| 6. |
|
Live and on demand content end-users delivery: The GMS can be seen as an edge node in the network, capable of deliver the contents to end-users using different technologies: GoalBit P2P streaming (through GBTP: GoalBit Transport Protocol), HTTP progressive download and other 3rd party technologies. |
|
|
EN
