The current approach is as follows:
1) User sends next action to OnLive.
2) OnLive renders the frame and sends it to the user.
3) Repeat.
The "faster than light" approach is:
1) OnLive renders several frames that could be the outcome of all the possible actions by the user, and sends all of them to the user.
2) User chooses the next action.
3) The frame is already available and is rendered ASAP.
4) The action is sent to OnLive.
5) Repeat.
It is of course not actually faster than light, but it's faster than the time required to send light to OnLive and back. Although, if you're going to this trouble, you may as well just render the frames locally and not bother with OnLive at all... :-S
Comments
The current approach is as follows: 1) User sends next action to OnLive. 2) OnLive renders the frame and sends it to the user. 3) Repeat.
The "faster than light" approach is: 1) OnLive renders several frames that could be the outcome of all the possible actions by the user, and sends all of them to the user. 2) User chooses the next action. 3) The frame is already available and is rendered ASAP. 4) The action is sent to OnLive. 5) Repeat.
It is of course not actually faster than light, but it's faster than the time required to send light to OnLive and back. Although, if you're going to this trouble, you may as well just render the frames locally and not bother with OnLive at all... :-S