Technology
The RTS System uses a newly developed technology called ‘AJAX Push’, which is also known as Streaming Push. Thanks to this innovative breakthrough, the server is able to send an update directly to the client who is watching the game, meaning data is available less than two seconds after an event has occurred. This allows us to achieve virtually a real-time communication between our match reporter at the stadium and our RTS player, thus improving both the quality and speed of the sportscast.
Implemented in Java, RTS is a real-time system, with every module developed as a stand-alone application. This is a vital development, as it allows for improved scalability in the future, which in turn gives us more scope to expand and improve our product. In addition to this, the RTS process functions superbly well with multiple computer systems and cores, rendering it ideal for larger businesses, as well as smaller companies.
The RTS system takes advantage of state-of-the-art load balancer in order to handle load and also to allow for graceful failover, should computer saturation or out of memory occur. This will therefore ensure that the RTS system is available at all times, regardless of problems that may arise.
Another advantage of the new RTS system is the minimalisation of bandwidth usage. As each update is sent individually, the bandwidth required is limited. Data sent is wrapped in JSON, which is a more compressed format, in comparison to XML.
The RTS system also comes in two versions, allowing clients to choose which is best suited to their individual or company needs:
- Web-based RTS player is able to update all the information sent, without having to constantly reload the page. However, perhaps it’s main advantage is that no other programs or software have to be added in order to run the system.
- Thick-client RTS player allows a more enhanced overall experience, due to higher quality graphics and more audio options. Within a few seconds, the user is able to launch, install and watch a live football game using the thick-client player.
