LOCATION INDEPENDENT EXECUTION OF USER INTERFACE OPERATIONS

• US 20110137909A1
• Filed: 12/07/2009
• Published: 06/09/2011
• Est. Priority Date: 12/07/2009
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Gross, Ran, Guertler, Jochen, Sherman, Yahali, Tammam, Ariel
• Application Number:
  US12/632,253
• Publication Number:
  US 20110137909A1
• Time in Patent Office: Days
• US Class Current: 707/741
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

This disclosure relates to systems, methods, and software that involve location-independent execution of user interface operations. This execution can include identifying a user interaction through a client-side user interface that is communicably coupled with a server-side computer. It is then dynamically determined whether to process the identified user interaction on the client-side or the server-side. If the user interaction is to be processed on the client-side, then a client-side action handler is invoked. If the user interaction is to be processed on the server-side, then it is requested that a server-side action handler process the interaction.

Claims

1. A computer-implemented method for location-independent execution of user interface operations, the method comprising the following steps executed by one or more processors:

identifying a user interaction through a client-side user interface that is communicably coupled with a server-side computer;

dynamically determining whether to process the identified user interaction on the client-side or the server-side;

if the user interaction is to be processed on the client-side, invoking a client-side action handler; and

if the user interaction is to be processed on the server-side, requesting that a server-side action handler process the interaction.

2. The computer implemented method of claim 1, where requesting that a server-side action handler process the interaction comprises:

determining whether the user interaction involves a synchronous or asynchronous action; and

requesting that one of a synchronous server-side action handler or an asynchronous server-side action handler process the interaction based on the determination.

3. The computer implemented method of claim 1, where dynamically determining whether to process the identified user interaction on the client-side or the server-side comprises utilizing a rules repository to determine whether to process the identified user interaction on the client-side or the server-side.

4. The computer implemented method of claim 3, where the rules repository includes a primary key that is mapped to the particular interaction.

5. The computer implemented method of claim 3, where the rules repository includes rules that store dynamic expressions of various interactions action.

6. The computer implemented method of claim 1, further comprising receiving the client-side action handler with user interface code from the server-side computer.

7. The computer implemented method of claim 1, the dynamic determination made, at least in part, according to a plurality of criteria, including processing capability, number of roundtrips, and operating environment.

8. A computer program product for location-independent execution of user interface operations, the computer program product comprising a tangible storage medium storing computer-readable instructions operable when executed to:

identify a user interaction through a client-side user interface that is communicably coupled with a server-side computer;

dynamically determine whether to process the identified user interaction on the client-side or the server-side;

if the user interaction is to be processed on the client-side, invoke a client-side action handler; and

if the user interaction is to be processed on the server-side, request that a server-side action handler process the interaction.

9. The computer program product of claim 8, where the stored instructions requesting that a server-side action handler process the interaction comprise stored instructions:

determining whether the user interaction involves a synchronous or asynchronous action; and

requesting that one of a synchronous server-side action handler or an asynchronous server-side action handler process the interaction based on the determination.

10. The computer program product of claim 8, where dynamically determining whether to process the identified user interaction on the client-side or the server-side comprises utilizing a rules repository to determine whether to process the identified user interaction on the client-side or the server-side.

11. The computer program product of claim 10, where the rules repository includes a primary key that is mapped to the particular interaction.

12. The computer program product of claim 10, where the rules repository includes rules that store dynamic expressions of various interactions action.

13. The computer program product of claim 8, where the stored instructions are further operable to receive the client-side action handler with user interface code from the server-side computer.

14. The computer program product of claim 8, the dynamic determination made, at least in part, according to a plurality of criteria, including processing capability, number of roundtrips, and operating environment.

15. The computer program product of claim 8, where the dynamic determination of whether to process the identified user interaction on the client-side or the server-side occurs for each event cycle where the user interaction involves multiple event cycles.

16. A computer system for communicating via a landscape aware inter-application communication infrastructure, the computer system comprising:

memory storing a client-side user interface and a client-side action handle; and

one or more processors that, when executed;

identify a user interaction through the client-side user interface that is communicably coupled with a server-side computer;

dynamically determine whether to process the identified user interaction on the client-side or the server-side;

if the user interaction is to be processed on the client-side, invoke the client-side action handler; and

if the user interaction is to be processed on the server-side, request that a server-side action handler process the interaction.

17. The computer system of claim 16, where the one or more processors requesting that a server-side action handler process the interaction comprises the one or more processors:

determining whether the user interaction involves a synchronous or asynchronous action; and

requesting that one of a synchronous server-side action handler or an asynchronous server-side action handler process the interaction based on the determination.

18. The computer system of claim 16, where the memory further stores a rules repository and where the one or more processors dynamically determine whether to process the identified user interaction on the client-side or the server-side by utilizing the rules repository.

19. The computer system of claim 18, where the rules repository includes a primary key that is mapped to the particular interaction.

20. The computer system of claim 18, where the rules repository includes rules that store dynamic expressions of various interactions action.

21. The computer system of claim 18, the one or more processors further operable to receive the client-side action handler with user interface code from the server-side computer.