DLI Implementation and Reference Guide - Datalogics

2.8 DLI Implementation and Reference Guide
defaults to 3 (PDF v1.3, for Adobe Acrobat v4 compatibility). If higher-level functions
are used within the output PDF document, the pdfMinorVer will be incremented as
appropriate to 4 or 5 (PDF v1.4 or PDF v1.5 respectively). You can force the declared
Concepts and Facilities: Guide to the DL Pager Composition System
Compliance Level by assigning the value you desire to pdfMinorVer within your
application.
Files In Memory Activation
To increase the throughput of PDF generation, memory-mapped files may be used for
temporary storage and for final output of the PDF content. Output of a PDF file to
both memory and disk is also supported for environments where this feature is
desired.
In order to utilize Files In Memory (FIM), DLI must be initialized through the
dlpdfinit function call, and the Datalogics memory file system must be passed to
this function call. The memory file system may be obtained by calling the
dlpdfmemfilesys function, detailed below (see “dlpdfmemfilesys” on page
2.11). This may be called before DLI (and, hence, the Adobe PDF Library) is
initialized. Once set, storage of temporary files in memory is automatic.
The DLI sample applications accompanying this release demonstrate the coding and
use of Files In Memory. It can be invoked by adding the command-line argument
MEMORY when calling the sample applications.
Initializing and Terminating via DLI
The following commands should be used to initialize and terminate the Adobe PDF
Library and DLI. In a single-threaded application, the initialization and termination
processes must be called only once during the life of the application. Attempting to
initialize the Adobe PDF Library and DLI more than once in the application may
cause errors or unpredictable behavior, and is not supported. (You are free to create
multiple documents and/or multiple files within the run, but the initialization and