Method for Distributing Computing Between Server and Client

• US 20080189358A1
• Filed: 03/16/2006
• Published: 08/07/2008
• Est. Priority Date: 03/16/2005
• Status: Active Grant

• Current Assignee: Airscape Technology Pty Limited
• Original Assignee: Airscape Technology Pty Limited
• Inventors: Charles, John Francis
• Granted Patent: US 8,280,947 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A method and system for use in running a display-based computer application, the computer application comprising a plurality of application segments, where computing is distributed between a server and a client computer. The method comprises the steps of providing a generic client engine (20) to the client computer, the client engine comprising an application manager (24), one or more display managers (22), and one or more load managers (26), providing a collection of individual application subset definition files (18), each relating to one of said application segments, wherein, on receipt of successive application subset definition files from the server, the client recursively transforms to provide the respective application segments. The invention has broad utility in a wide variety of display-based computer applications, particularly in wireless applications.

Claims

1. A method for use in running a display-based computer application, the application comprising a plurality of application segments, involving distributing computing between a server on a server computer and a client on a client computer, the server and client computers operatively interconnected by way of a computer network, the method comprising the steps of:

(a) providing a generic client engine to the client computer, the client engine comprising an application manager, one or more display managers, and one or more load managers;

(b) providing a collection of individual application subset definition files each relating to one of said application segments;

(c) wherein, on receipt of successive application subset definition files from the server, the client recursively transforms to provide the respective application segments.

2. The method according to claim 1, wherein an application subset definition file defines components or layout characteristics within one or more display areas associated with the respective segment.

3. The method according to claim 2, wherein an application subset definition file defines only information relating to component or layout characteristics to be added or removed between successive client updates.

4. The method according to claim 1, wherein the application definition files are formatted in an application definition mark-up language.

5. The method according to claim 1, wherein the application manager is adapted to run as a separate client-side layer, to manage variables associated with each application segment, the application manager including:

(a) controlling means for controlling interaction between resident display areas;

(b) loading means for asynchronous loading of images into display areas;

(c) caching means for controlling caching of images; and

(d) parsing means for parsing application subset definition files.

6. The method according to claim 5, wherein the parsing means is adapted for parsing compressed application definition files.

7. The method according to claim 5, wherein the caching means includes means to destroy in the client memory, after a cache period, cached images for an application segment when initiating the caching of cached images for a subsequent application segment.

8. The method according claim 1, wherein the application manager includes one or more of:

(a) gateway placeholder means for short-duration instantiated objects;

(b) memory management means between application subset transitions;

(c) storage means for hash tables, arrays and variables; and

(d) interface means to online/offline cache control management classes.

9. The method according to claim 1, wherein the one or more display managers include one or more of the following components:

(a) initialisation and construction means;

(b) component and sub-component layout means;

(c) data validation means;

(d) event handling means;

(e) means for data synchronisation across display subset transitions both internally within an application subset and externally across application subsets; and

(f) means for storage of component or container objects and associated component or container information.

10. The method according to claim 1, wherein the one or more load managers include one or more of the following components:

(a) url parser means to asynchronously load and parse remote application subset definition files by way of url parser threads;

(b) watchdog means configured to be instantiated by the url parser means to perform a timeout on a url parser thread; and

(c) loader means configured to be instantiated at the end of a url parser thread lifespan.

11. The method according to claim 1, wherein the generic client engine hither includes one or more publication managers, configured to periodically check the connection status with said server computer and to invoke delivery of client-side stored data to the server computer.

12. The method according to claim 1, implemented in a browser-independent manner.

13. A computer program embodied on a computer readable medium for carrying out the method according to claim 1.

14. A distributed computing system for running a display-based computer application, the application comprising a plurality of application segments, the system comprising:

(a) a client device;

(b) a server computer operatively interconnected to the client device by way of a computer network;

(c) a generic client engine installed on the client device, the client engine comprising an application manager, one or more display managers, and one or more load managers; and

(d) a collection of individual application subset definition files each relating to one of said application segments;

wherein the client device is configured to recursively transform to provide the respective application segments on receipt of successive application subset definition files from the server computer.

15. The system according to claim 14, wherein an application subset definition file defines components or layout characteristics within one or more display areas associated with the respective segment.

16. The system according to claim 15, wherein an application subset definition file defines only information relating to component or layout characteristics to be added or removed between successive client updates.

17. The system according to claim 14, wherein the application manager is adapted to run as a separate client-side layer, to manage variables associated with each application segment, the application manager including:

(a) controlling means for controlling interaction between resident display areas;

(b) loading means for asynchronous loading of images into display areas;

(c) caching means for controlling caching of images; and

(d) parsing means for parsing application subset definition files.

18. The system according to claim 17, wherein the parsing means is adapted for parsing compressed application definition files.

19. The system according to claim 17, wherein the caching means includes means to destroy in the client memory cached images for an application segment when initiating the caching of cached images for a subsequent application segment.

20. The system according to claim 14, wherein the application manager includes one or more of:

(a) gateway placeholder means for short-duration instantiated objects;

(b) memory management means between application subset transitions;

(e) storage means for hash tables, arrays and variables; and

(d) interface means to online/offline cache control management classes.

21. The system according to claim 14, wherein the one or more display managers include one or more of the following components:

(a) initialisation and construction means;

(b) component and sub-component layout means;

(c) data validation means;

(d) event handling means;

(e) means for data synchronization across display subset transitions both internally within an application subset and externally across application subsets; and

(f) means for storage of component or container objects and associated component or container information.

22. The system according to claim 14, wherein the one or more load managers include one or more of the following components:

(a) url parser means to asynchronously load and parse remote application subset definition files by way of url parser threads;

(b) watchdog means configured to be instantiated by the url parser means to perform a timeout on a url parser thread; and

(c) loader means configured to be instantiated at the end of a url parser thread lifespan.

23. The method according to claim 14, wherein the generic client engine further includes one or more publication managers, configured to periodically check the connection status with said server computer and to invoke delivery of client-side stored data to the server computer.