Scene-isolated internet application

• US 9,785,560 B2
• Filed: 04/21/2014
• Issued: 10/10/2017
• Est. Priority Date: 04/19/2013
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Woods, Joshua Michael
• Primary Examiner(s): Hoang, Phi
• Application Number:
  US14/257,844
• Publication Number:
  US 20140313215A1
• Time in Patent Office: 1,268 Days
• CPC Class Codes: G06F 12/0862 with prefetch
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

Computer-implemented systems, methods and apparatus are provided for rendering different scenes of an application. An application framework is provided that includes a scene controller and a scene cache pre-fetch module that stores at least some of the different scenes as cached scenes. When the scene controller receives a request for a new scene (e.g., to change the current active scene) it can determine whether that new scene is stored at the scene cache pre-fetch module. If so, the scene controller can load the cached scene directly from the scene cache pre-fetch module as a new active scene.

Claims

1. A computer-implemented system, comprising:

a memory configured to store computer-executable instructions of;

a rich Internet application comprising;

a plurality of scenes capable of being presented as a user interface of the rich Internet application, wherein the rich Internet application is configured to load and render different scenes in response to interaction with the rich Internet application, wherein each scene is a portion of the rich Internet application that is active when loaded to render an active portion of content of the rich Internet application at a browser until a new scene is selected, and wherein each scene comprises;

an IFrame having unique application data associated therewith that defines content and characteristics that are unique to that scene, and associated application logic unique to that scene and for rendering each scene; and

a set of shared libraries and core logic specific to the rich Internet application that are used to render common portions that are the same in each scene of the rich Internet application;

an application framework integrated with the rich Internet application, the application framework comprising;

a persisted controller comprising;

a scene controller that is designed to receive requests to change an active scene that is currently active as the user interface of the rich Internet application; and

a shared library and core logic controller configured to access and load the set of shared libraries and core logic to render common portions that are the same in each scene of the rich Internet application; and

a scene cache pre-fetch module communicatively coupled to and controlled by the scene controller, wherein the scene controller communicates with the scene cache pre-fetch module using inter-process communications, the scene cache pre-fetch module being designed to store particular ones of the plurality of scenes that are inactive as cached scenes, and

wherein the scene controller is configured to;

serve as an isolation boundary that isolates the cached scenes stored at the scene cache pre-fetch module from the active scene that is currently being presented via the user interface; and

when a cached scene is selected, load the cached scene directly from the scene cache pre-fetch module as a new active scene to thereby reduce delay normally associated with loading; and

a processor communicatively coupled to the memory and capable of executing the computer-executable instructions.

2. A computer-implemented system according to claim 1, wherein the scene cache pre-fetch module is further designed to store application data associated with each of cached scenes.

3. A computer-implemented system according to claim 1, wherein the set of shared libraries and core logic are configured as part of the rich Internet application and are temporarily stored by the shared library and core logic controller.

4. A computer-implemented system according to claim 1, wherein the user interface comprises:

a persisted user interface that is capable of;

storing persistent content that is common to each scene of the rich Internet application;

presenting the persistent content as the user interface in conjunction with each scene of the rich Internet application;

temporarily storing application data associated with the active scene; and

presenting the active scene that is currently active via the user interface.

5. A computer-implemented method for rendering different scenes as a user interface of a rich Internet application comprising a plurality of scenes and set of shared libraries and core logic, wherein the rich Internet application is configured to load and render different scenes in response to interaction with the rich Internet application, wherein each scene is a portion of the rich Internet application that is active when loaded to render an active portion of content of the rich Internet application at a browser until a new scene is selected, and, wherein each scene comprises:

an IFrame having unique application data associated therewith that defines content and characteristics that are unique to that scene, and associated application logic unique to that scene and for rendering each scene, wherein the set of shared libraries and core logic are specific to the rich Internet application and used to render common portions that are the same in each scene of the rich Internet application, the computer-implemented method comprising;

loading an application framework integrated with the rich Internet application and initializing the application framework by loading a starting scene as a current active scene as the user interface, wherein the application framework comprises;

a persisted controller comprising;

a scene controller that is designed to receive requests to change an active scene that is currently active as the user interface of the rich Internet application; and

a shared library and core logic controller configured to access and load the set of shared libraries and core logic to render common portions that are the same in each scene of the rich Internet application; and

a scene cache pre-fetch module communicatively coupled to and controlled by the scene controller, wherein the scene cache pre-fetch module being designed to store particular ones of the plurality of scenes that are inactive as cached scenes, and wherein the scene controller is configured to;

serve as an isolation boundary that isolates the cached scenes stored at the scene cache pre-fetch module from the active scene that is currently being presented via the user interface;

receiving, at the scene controller a request for a new scene that is different than the current active scene being rendered as the user interface;

determining, at the scene controller whether the new scene being requested is stored as a cached scene at the scene cache pre-fetch module that stores at least some of the plurality of scenes as cached scenes that are isolated from the current active scene that is currently being rendered as the user interface, wherein the scene controller communicates with the scene cache pre-fetch module using inter-process communications; and

when the new scene being requested is determined to be stored as a cached scene at the scene cache pre-fetch module;

loading, at the scene controller directly from the scene cache pre-fetch module using inter-process communications, the cached scene as a new active scene at the user interface to thereby reduce delay normally associated with loading.

6. A computer-implemented method according to claim 5,

wherein the cached scenes are capable of being loaded by the scene controller.

7. A computer-implemented method according to claim 5, further comprising:

after determining that the new scene being requested is stored as a cached scene at the scene cache pre-fetch module storing the starting scene as one of the cached scenes at the scene cache pre-fetch module.

8. A computer-implemented method according to claim 5, further comprising:

when the new scene being requested is determined to not be stored as one of the cached scenes at the scene cache pre-fetch module;

loading, at the scene controller from a server, a fresh instance of the new scene being requested as the new active scene as the user interface.

9. A computer-implemented method according to claim 5, wherein the scene cache pre-fetch module is further designed to store application data associated with each of cached scenes.

10. A computer-implemented method according to claim 5, wherein the set of shared libraries and core logic are configured as part of the rich Internet application and are temporarily stored by the shared library and core logic controller.

11. A computer-implemented method according to claim 5, further comprising:

storing, at a persisted user interface of the user interface, persistent content that is common to each scene of the rich Internet application;

presenting, via the persisted user interface, the persistent content as the user interface in conjunction with each scene of the application;

temporarily storing, at the persisted user interface of the user interface, application data associated with the active scene; and

presenting the active scene that is currently active via the user interface.

12. A non-transitory computer readable storage media comprising:

computer instructions to implement the computer-implemented method of claim 5.

13. A computing device comprising a processor and a memory, wherein the memory comprises computer-executable instructions that, when executed by the processor, cause the computing device to execute a rich Internet application to render different scenes of a plurality of scenes as a user interface of the rich Internet application, wherein the rich Internet application comprises the plurality of scenes and set of shared libraries and core logic, wherein the rich Internet application is configured to load and render different scenes in response to interaction with the rich Internet application, wherein each scene is a portion of the rich Internet application that is active when loaded to render an active portion of content of the rich Internet application at a browser until a new scene is selected, wherein each scene comprises:

an IFrame having unique application data associated therewith that defines content and characteristics that are unique to that scene and associated application logic unique to that scene and for rendering each scene, wherein the set of shared libraries and core logic are specific to the rich Internet application and used to render common portions that are the same in each scene of the rich Internet application, wherein execution of the computer-executable instructions by the processing system causes the computing device to;

load an application framework integrated with the rich Internet application, the application framework comprising a persisted controller comprising;

a scene controller that is designed to receive requests to change an active scene that is currently active as the user interface of the rich Internet application; and

a shared library and core logic controller configured to access and load the set of shared libraries and core logic to render common portions that are the same in each scene of the rich Internet application; and

a scene cache pre-fetch module communicatively coupled to and controlled by the scene controller, wherein the scene cache pre-fetch module being designed to store particular ones of the plurality of scenes that are inactive as cached scenes, and wherein the scene controller is configured to;

serve as an isolation boundary that isolates the cached scenes stored at the scene cache pre-fetch module from the active scene that is currently being presented via the user interface,

initialize the application framework by loading a starting scene as a current active scene as the user interface;

receive, at the scene controller, a request for a new scene that is different than the current active scene being rendered as the user interface, wherein the current active scene that is currently being rendered as the user interface is isolated from the cached scenes;

determine, at the scene controller, whether the new scene being requested is stored as a cached scene at the scene cache pre-fetch module that stores at least some of the plurality of scenes as cached scenes that are isolated from the current active scene that is currently being rendered as the user interface, wherein the scene controller communicates with the scene cache pre-fetch module using inter-process communications; and

when the new scene being requested is determined to be stored as a cached scene at the scene cache pre-fetch module;

load, at the scene controller directly from the scene cache pre-fetch module using inter-process communications, the cached scene as a new active scene at the user interface to thereby reduce delay normally associated with loading.

14. A computer program product for use with a computer including a display for presenting a user interface of a rich Internet application, the computer program product comprising a non-transitory computer readable medium having a computer readable program code embodied therein for controlling the user interface of the application, the computer program product comprising:

wherein the rich Internet application comprises;

a plurality of scenes capable of being presented as the user interface of the rich Internet application, wherein the rich Internet application is configured to load and render different scenes in response to interaction with the rich Internet application, wherein each scene is a portion of the rich Internet application that is active when loaded to render an active portion of content of the rich Internet application at a browser until a new scene is selected, and wherein each scene comprises;

an IFrame having unique application data associated therewith that defines content and characteristics that are unique to that scene, and associated application logic unique to that scene and for rendering each scene;

a set of shared libraries and core logic specific to the rich Internet application that are used to render common portions that are the same in each scene of the rich Internet application; and

an application framework integrated with the rich Internet application, the application framework comprising;

a persisted controller comprising;

a scene controller that is designed to receive requests to change an active scene that is currently active as the user interface of the rich Internet application; and

a shared library and core logic controller configured to access and load the set of shared libraries and core logic to render common portions that are the same in each scene of the rich Internet application; and

a scene cache pre-fetch module communicatively coupled to and controlled by the scene controller, wherein the scene controller communicates with the scene cache pre-fetch module using inter-process communications, the scene cache pre-fetch module being designed to store particular ones of the plurality of scenes that are inactive as cached scenes, and

wherein the scene controller is configured to;

serve as an isolation boundary that isolates the cached scenes stored at the scene cache pre-fetch module from the active scene that is currently being presented via the user interface; and

when a cached scene is selected, load the cached scene directly from the scene cache pre-fetch module as a new active scene to thereby reduce delay normally associated with loading.