Browse Prior Art Database

A System for Developing User Interface Event Handlers for Rich Client Applications

IP.com Disclosure Number: IPCOM000032971D
Original Publication Date: 2004-Nov-19
Included in the Prior Art Database: 2004-Nov-19
Document File: 1 page(s) / 29K

Publishing Venue

IBM

Abstract

Disclosed is a system for developing user interface event handlers for rich client applications by modeling event handler business logic as service choreography.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 1

A System for Developing User Interface Event Handlers for Rich Client Applications

Rich client applications are those in which a server delivers rich user interface functionality directly to a client system. Currently there is a framework for providing rich UI to client systems, specifically, a web browser. This framework utilizes data models for server business logic programming, then delivers those models and the corresponding data instances directly to the client for further manipulation. Any number of operations can occur on the client, until the data is submitted back to the server as a delta against the server copy. This system is known as the Faces client.

UI controls sit in the faces client which are tied directly to data objects for the purpose of basic CRUD operations. For instance, a data table control can allow one to page through multiple rows of data without going back to the server. It can also expose a delete operate for a particular row, or allow you modify a row, or even add a new row. Say you wish to add a button that performs a more complex manipulation on a given data object. Today, you must implement that function manually as javascript which accesses UI components and data

Today it is possible to represent complex operations with data as a process flow. These flows can also invoke external services (possibly implemented by other flows), depending on their accessibility from the flow's runtime environment. Such a flow can be modeled, and therefore, tooled against. These flows can be executed on the server and provide the interface to the flow through a service interface.

We propose reusing this development paradigm such that a flow is modeled as the handler for a UI event. This flow can manipulate all the available persistent data in the client by exposing them as variables in the process. The flow can support operations on other UI components as external entities (which in turn may have their own UI event handler processes). The flow could even invoke external services if such a service client can be exploited in the client environment (such as invoking web services from javascript). The flow can be deployed to the client and linked to the UI component by compiling the flow to client-side code.

The advantage of this system is that we can use tools for modeling process flows, allo...