Markup method for managing rich client code and experiences using multi-component pages

• US 7,734,686 B2
• Filed: 01/25/2005
• Issued: 06/08/2010
• Est. Priority Date: 01/25/2005
• Status: Active Grant

• Current Assignee: Twitter Inc (X Holdings Corp.)
• Original Assignee: International Business Machines Corporation
• Inventors: Calow, Jeffrey T., Wilson, Douglass J., Wilson, Richard M., Kraenzel, Carl J.
• Primary Examiner(s): Nawaz; Asad M
• Application Number:
  US11/042,432
• Publication Number:
  US 20060168512A1
• Time in Patent Office: 1,960 Days
• Field of Search: 709202-207, 709217-230, 709/238, 463/1, 715/205, 715234-243, 715/760
• US Class Current: 709/203
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/2895 Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A mark-up method and system that enables server-managed thick client capabilities using a thin client server, framework, and administration. Active content such as program code, service, and data components, are driven to a thick client platform. The thick client platform is defined through a combination of thick client components, while the thick client components and user interface experience are centrally managed. The thick client container can operate to embed thin client container components, such as a browser, and the thick client container itself can be initially deployed over a network using a thin client.

Claims

1. A method of providing a thick client application platform on a client computer system, comprising:

receiving a page request at a server computer system;

detecting, by said server computer system, that said request is on behalf of said thick client application platform, wherein at least one thin client application container component is embedded within said thick client application platform;

selecting, by said server computer system, responsive to said detecting that said request is on behalf of said thick client application platform, a thick client mark-up document reflecting attributes of a user associated with said request, wherein said attributes are managed through said server computer system;

sending said selected thick client mark-up document to said client computer system; and

loading a workspace component to said client computer system, wherein said workspace component is operable to communicate with a services layer on said server computer system in support of said thick client platform.

2. The method of claim 1, further comprising:

detecting, at said client computer system, that at least one application component referenced by said thick client mark-up document is not stored on said client computer system; and

responsive to said detecting that said at least one application component referenced by said thick client mark-up document is not stored on said client computer system, requesting said at least one application component from said server computer system.

3. The method of claim 2, further comprising:

loading a local component catalog onto said client computer system; and

wherein said detecting that at least one application component referenced by said thick client mark-up document is not stored on said client computer system is responsive to said local component catalog.

4. The method of claim 1, further comprising:

loading a user interface component to said client computer system for use with said thick client platform, wherein said user interface component is operable to provide user interface display objects within said thick client application platform by executing program code on said client computer system.

5. The method of claim 1, wherein said attributes of said user include access rights corresponding to at least one application component provided by said server computer system through said thick client application platform.

6. The method of claim 1, wherein said attributes of said user include settings describing at least one aspect of a user interface display screen to be provided to said user through said thick client application platform.

7. The method of claim 1, wherein said at least one thin client application container component comprises a Web browser.

8. A system comprising:

at least one computer readable memory, said computer readable memory having stored thereon program code for providing a thick client application platform on a client computer system, said program code when executed performing the steps of

receiving a page request at a server computer system,

detecting, by said server computer system, that said request is on behalf of said thick client application platform, wherein at least one thin client application container component is embedded within said thick client application platform,

selecting, by said server computer system, responsive to said detecting that said request is on behalf of said thick client application platform, a thick client mark-up document reflecting attributes of a user associated with said request, wherein said attributes are managed through said server computer system,

sending said selected thick client mark-up document to said client computer system, and

loading a workspace component to said client computer system, wherein said workspace component is operable to communicate with a services layer on said server computer system in support of said thick client platform.

9. The system of claim 8, said program code when executed further performing the steps of:

detecting, at said client computer system, that at least one application component referenced by said thick client mark-up document is not stored on said client computer system; and

responsive to said detecting that said at least one application component referenced by said thick client mark-up document is not stored on said client computer system, requesting said at least one application component from said server computer system.

10. The system of claim 9, said program code when executed further performing the steps of:

loading a local component catalog onto said client computer system; and

wherein said detecting that at least one application component referenced by said thick client mark-up document is not stored on said client computer system is responsive to said local component catalog.

11. The system of claim 8, said program code when executed further performing the steps of:

loading a user interface component to said client computer system for use with said thick client platform, wherein said user interface component is operable to provide user interface display objects within said thick client application platform by executing program code on said client computer system.

12. The system of claim 8, wherein said attributes of said user include access rights corresponding to at least one application component provided by said server computer system through said thick client application platform.

13. The system of claim 8, wherein said attributes of said user include settings describing at least one aspect of a user interface display screen to be provided to said user through said thick client application platform.

14. A computer program product, comprising:

a computer readable memory, said computer readable memory having stored thereon program code for providing a thick client application platform on a client computer system, said program code when executed performing the steps of

receiving a page request at a server computer system,

detecting, by said server computer system, that said request is on behalf of said thick client application platform, wherein at least one thin client application container component is embedded within said thick client application platform,

selecting, by said server computer system, responsive to said detecting that said request is on behalf of said thick client application platform, a thick client mark-up document reflecting attributes of a user associated with said request, wherein said attributes are managed through said server computer system,

sending said selected thick client mark-up document to said client computer system, and

loading a workspace component to said client computer system, wherein said workspace component is operable to communicate with a services layer on said server computer system in support of said thick client platform.