Pre-loading translated code in cloud based emulated applications
Pre-translated code for an emulated application may be retrieved and executed to translate data from the emulated application into a form compatible with the client device before receiving a request for the emulated application from the client device. The translated data may be delivered to the client device platform over a network after receiving the request for the emulated application from the client device.
1. A nontransitory computer readable medium containing executable program, wherein execution of the program instructions by one or more processors of a computer system causes the one or more processors to implement a method comprising:
retrieving a platform independent recording of a state of an emulator at a point during emulation of a legacy application before receiving a request for the legacy application from a client device;
executing the emulator with the platform independent recording of the state of the emulator to translate data from the legacy application into a form compatible with the client device; and
delivering the translated data to the client device platform over a network.
2. The nontransitory computer readable medium of claim 1 , wherein the legacy application is a legacy game.
3. The nontransitory computer readable medium of claim 1 , wherein the memory is a cache.
4. The nontransitory computer readable medium of claim 1 , wherein the platform independent recording of the state of the emulator is loaded before a request for the legacy application is made by the client device platform.
5. The nontransitory computer readable medium of claim 1 , wherein the method further comprises choosing which legacy application of a plurality of legacy applications to pre-load with a prediction engine.
6. The nontransitory computer readable medium of claim 5 , wherein the prediction engine uses historical data of the number of client device platforms that have made a request for the legacy application in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
7. The nontransitory computer readable medium of claim 6 , wherein the historical data further includes a time and date with each request for the legacy application.
8. The nontransitory computer readable medium of claim 5 , wherein the prediction engine uses data from a user profile associated with the client device platform that is searching for an emulated application in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
9. The nontransitory computer readable medium of claim 5 , wherein the prediction engine uses triggers from a second application that is being played by the client device platform in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
10. The nontransitory computer readable medium of claim 5 , wherein the prediction engine tracks the client device platform as it navigates an application selection menu in order to choose which legacy application to pre-load the platform independent recording of a state of the emulator.
11. The nontransitory computer readable medium of claim 10 , wherein the prediction engine follows a cursor controlled by the client device platform in order to track the navigation.
12. The nontransitory computer readable medium of claim 10 , wherein the prediction engine follows one or more eyes belonging to a user controlling the client device platform in order to track the navigation.
13. An emulator configured to operate on a network, comprising:
one or more processors;
a memory coupled to the one or more processors;
one or more executable instructions embodied in memory, the instructions being configured to implement a method when executed by the one or more processors, the method comprising:
retrieving a platform independent recording of a state of an emulator at a point during emulation of a legacy application before receiving a request for the legacy application from a client device;
executing the emulator with the platform independent recording of the state of the emulator to translate data from the legacy application into a form compatible with the client device; and
delivering the translated data to the client device platform over a network.
14. The emulator of claim 13 , wherein the legacy application is a legacy game.
15. The emulator of claim 13 , wherein the memory is a cache.
16. The emulator of claim 13 , wherein the platform independent recording of the state of the emulator is loaded before a request for the legacy application is made by the client device platform.
17. The emulator of claim 13 , wherein the method further comprises choosing which legacy application of a plurality of legacy applications to pre-load with a prediction engine.
18. The emulator of claim 17 , wherein the prediction engine uses historical data of the number of client device platforms that have made a request for the legacy application in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
19. The emulator of claim 18 , wherein the historical data further includes a time and date with each request for the emulated application.
20. The emulator of claim 17 , wherein the prediction engine uses data from a user profile associated with the client device platform that is searching for a legacy application in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
21. The emulator of claim 17 , wherein the prediction engine uses triggers from a second application that is being played by the client device platform in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
22. The emulator of claim 17 , wherein the prediction engine tracks the client device platform as it navigates an application selection menu in order to choose which legacy application to pre-load the platform independent recording of the state of the emulator.
23. The emulator of claim 22 , wherein the prediction engine follows a cursor controlled by the client device platform in order to track the navigation.
24. The emulator of claim 22 , wherein the prediction engine follows one or more eyes belonging to a user controlling the client device platform in order to track the navigation.
25. In an emulator configured to operate on a network, a method, comprising:
retrieving a platform independent recording of the state of an emulator at a point during emulation of a legacy application before receiving a request for the emulated application from a client device;
executing the emulator with the platform independent recording of the state of the emulator to translate data from the legacy application into a form compatible with the client device; and
delivering the translated data to the client device platform over the network.