Progress
Client Deployment
Guide


Library Overview

Progress provides two types of r-code libraries: standard and memory-mapped. A standard library contains r-code procedures that execute in local memory. A memory-mapped library contains r-code procedures that execute in shared memory.

When you execute r-code procedures from either a standard library in local memory or a memory-mapped library in shared memory, you gain the following advantages:

When you execute r-code procedures from a memory-mapped library in shared memory, you gain the following additional advantages:

When loading and executing r-code procedures from operating system files in a directory, Progress must open and close each file individually. When loading and executing r-code procedures from standard or memory-mapped libraries, Progress opens only one file—the library itself—to access all of the r-code files in the library.

The r-code files that you place in a library are called members. Progress opens a library the first time you run a member procedure from the library. The library stays open until the end of your Progress session or until you remove the library from the PROPATH. For more information about how standard and memory-mapped libraries interact with PROPATH during a Progress session, see the "Libraries and PROPATH" section later in this chapter.

For information about monitoring and optimizing r-code execution during a Progress client session, see Managing Client Performance." For more information about r-code structure and execution, see the Progress Programming Handbook.


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