** just so you know - I'm about as biased as possible on this subject. **
A technically better solution is available, and its not even rocket science. The casino software could (and should) do version managmenet on each of its components. When a component is updated on the backend, the server could generate a 'patch' containing just the differences between the two versions and send that to the player. This would reduce network traffic to just a fraction of the total size, with slightly bigger updates if more things actually have changed.
Not only does this system allow for much faster updates, regular players will get the updates in small patches as they happen, and only players that have not run the software in a long time would get bigger updates. In any scenario there's no need to send entire files to any players. (enabling even modem
players to actually stay up to date.)
With this issue become a real annoyance to the players, one would expect a big player like
mg to have a more technically updated solution. Some competitors certainly are using this technique

Bookmarks