22.03.2015 Views

DLI Implementation and Reference Guide - Datalogics

DLI Implementation and Reference Guide - Datalogics

DLI Implementation and Reference Guide - Datalogics

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>DLI</strong> <strong>Reference</strong> <strong>Guide</strong> A.91<br />

Technical Notes<br />

1 Initialization of <strong>DLI</strong> is now required; support for using <strong>DLI</strong> without initialization<br />

has been removed. If you intend to use <strong>DLI</strong> methods in your application, you must<br />

intialize <strong>DLI</strong> via dlpdfinit. <strong>DLI</strong> users should initialize the Adobe PDF Library<br />

through the <strong>DLI</strong> initialization call; PDFLInit <strong>and</strong> PDFLTerm should never be<br />

directly called from a <strong>DLI</strong> application.<br />

2 In a multi-threaded application, each thread must do its own initialization <strong>and</strong><br />

termination of the Library.<br />

3 This procedure, along with dlpdfterm, replaces the need for calls to PDFLInit<br />

<strong>and</strong> PDFLTerm. <strong>DLI</strong> should be initialized, or the Adobe PDF Library, but not<br />

both.<br />

4 You can accidentally call dlpdfinit (the <strong>DLI</strong> comm<strong>and</strong>) multiple times without<br />

problems, as it contains internal code that prevents actual initialization from<br />

occurring more than once, but you cannot call PDFLInit (the Adobe PDF<br />

Library comm<strong>and</strong>) more than once as a fatal error will occur.<br />

5 dlpdfinit <strong>and</strong> dlpdfterm are the only methods which must not be enclosed in<br />

exception h<strong>and</strong>lers (i.e. DURING/HANDLER/END_HANDLER statements), because<br />

they are not set up before initialization, <strong>and</strong> are freed during termination.<br />

6 As of <strong>DLI</strong> v3.0.11, the <strong>DLI</strong> graphics cache has been enhanced to use the default<br />

ASFileSys implementation provided to dlpdfinit for caching graphics. By<br />

default, the graphics cache file size is limited to 1.5GB. Customers who wish to use<br />

larger graphics cache files are advised to supply a filesystem to dlpdfinit which<br />

is capable of reliably h<strong>and</strong>ling files of the larger size.<br />

NOTE: The cache size limit is checked every time a document is destroyed; the<br />

cache may therefore temporarily exceed the cache size limit. When setting the<br />

cache size limit, please note that to resize the graphics cache, free space equal to<br />

the sum of the cache limit <strong>and</strong> the "low water" mark is required. Files In Memory<br />

users with large graphics workloads are advised to lower the cache size limit to a<br />

number appropriate for their target environment.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!