Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Graphical Data Exchange Protocol

IP.com Disclosure Number: IPCOM000036148D
Original Publication Date: 1989-Sep-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Franklin, SM: AUTHOR [+2]

Abstract

This article describes a method for implementing a protocol to manage the exchange of graphical data in realtime within a multi-tasked environment. The Graphical Data Exchange (GDE) Protocol provides the capability for independent applications executing as separate processes to interchange arbitrary amount of data ranging from small acknowledgement message to huge amounts of descriptive graphics data in a consistent manner across both process and system boundaries.

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

Page 1 of 1

Graphical Data Exchange Protocol

This article describes a method for implementing a protocol to manage the exchange of graphical data in realtime within a multi-tasked environment. The Graphical Data Exchange (GDE) Protocol provides the capability for independent applications executing as separate processes to interchange arbitrary amount of data ranging from small acknowledgement message to huge amounts of descriptive graphics data in a consistent manner across both process and system boundaries.

The Dynamic Data Exchange (DDE) protocol is an existing, defined protocol in the Microsoft Windows environment for passing data dynamically between applications. However, existing protocols such as DDE are unable to suitably pass data between applications in a multi- tasking environment. Furthermore, such protocols are generally inconsistent in their conventions. When an application broadcasts a conversation initiation message in DDE, it identifies the topic and target application by using global system memory hash tables (atoms). However, in a multi-tasking environment, such as the IBM OS/2*, receiving applications must know the handle to the atom table before they can look up the atoms and hash the strings. This implies that an additional message must be broadcast before DDE conversations are initiated, and ALL applications participating in any DDE conversation must access the atom table and decode the strings before determining if the message was intended for them. In DDE, once the atom tab...