Release 10.1A: OpenEdge Development:
Programming Interfaces

> ## Named Pipes

> In the UNIX and Windows environments, you can establish interprocess communications (IPC) between a non-OpenEdge application (such as a C program or commercial software package) and a OpenEdge session using named pipes. This facility provides a capability similar to Dynamic Data Exchange (DDE) in Windows, though it works very differently. Named pipes provide a general exchange mechanism for text data. Any data you can access as a character string within OpenEdge, you can read or write to a named pipe.

> OpenEdge accesses named pipes already created on your UNIX or Windows systems. OpenEdge does not create a named pipe itself. Named pipes are only valid on UNIX or Windows systems. This can pose a portability issue.

> From the Progress 4GL, named pipes look and act like operating system files. To exchange data, the OpenEdge application reads or writes to a named pipe, just as it does to a file. However, instead of a file at the end of the pipe, the non-OpenEdge application reads or writes data to the OpenEdge application.

> This chapter contains the following sections:

> - Overview of named pipes with Progress

> - UNIX named pipes

> - Windows named pipes

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095