Raymond C Holmes

US Patent:

7805730, Sep 28, 2010

Filed:

Sep 21, 2006

Appl. No.:

11/533900

Inventors:

Raymond Douglas Holmes - Forest Hills NY, US
Kwok Ping Leung - Singapore, SG
Mike Tyldesley - Singapore, SG
Adrian Chua Tze Hou - Singapore, SG
Nicholas Kolba - Montclair NJ, US

Assignee:

Reuters America, LLC - New York NY

International Classification:

G06F 3/00
G06F 9/44
G06F 9/46
G06F 13/00

US Classification:

719316, 719320

Abstract:

A Common Component Framework (CCF) provides a container interface and a component interface for communication in a multi-tiered software application. Component context data may be transmitted to and from a container describing a current state of a component executing within the container. Context data may correspond to a specific entity (e. g. , a financial entity such as a company or stock) identified by a user interacting with the component. The container may communicate the context data between different components to synchronize and coordinate component behavior, providing a more robust and coherent user experience. In addition to component context data, other information may be transmitted between containers and components such as properties, menu options, and data fields, supporting more complete integration of even web-based components into containers.

US Patent:

8578395, Nov 5, 2013

Filed:

Aug 27, 2010

Appl. No.:

12/870018

Inventors:

Raymond Douglas Holmes - Forest Hills NY, US
Kwok Ping Leung - Bukit Batok Central, SG
Mike Tyldesley - Singapore, SG
Adrian Chua Tze Hou - Singapore, SG
Nicholas Kolba - New York NY, US

Assignee:

Reuters America, LLC. - New York NY

International Classification:

G06F 3/00
G06F 9/44
G06F 9/46
G06F 13/00

US Classification:

719316, 719313, 719315

Abstract:

A Common Component Framework (CCF) provides a container interface and a component interface for communication in a multi-tiered software application. Component context data may be transmitted to and from a container describing a current state of a component executing within the container. Context data may correspond to a specific entity (e. g. , a financial entity such as a company or stock) identified by a user interacting with the component. The container may communicate the context data between different components to synchronize and coordinate component behavior, providing a more robust and coherent user experience. In addition to component context data, other information may be transmitted between containers and components such as properties, menu options, and data fields, supporting more complete integration of even web-based components into containers.