Q: I have just downloaded the trial SDK for PDFNet. It has been by far
the best I have found in terms of ease of use. The samples are
excellent.
I have a couple of technical questions relating to security that I
would need to know before purchasing. Please could you tell me:
1. If I don’t provide a means of saving a PDF (e.g. a save button,
linking to the PDFViewCtrl.GetDoc().Save()), will it still be possible
for users to save the document in any way? The Adobe 10 reader has no
way of disabling the ‘save a copy’ feature and we need to have full
control over this.
2. Is the PDFNet .dll saving a document anywhere to the hard drive?
E.g. If I were to set a PDFDoc with a stream or byte array, will a
copy (in any form) be saved to the user’s hard drive, or will it ever
be possible to access that document from the user’s hard drive?
--------------------------------
A: ➢ If I don’t provide a means of saving a PDF (e.g. a save button,
linking to the PDFViewCtrl.GetDoc().Save()),
➢ will it still be possible for users to save the document in any way?
The Adobe 10 reader has no way
➢ of disabling the ‘save a copy’ feature and we need to have full
control over this.
Unlike Acrobat Reader, with PDFNet you have full control over the
application logic in your application. So if you do not expose option
to save a document, users will not be able to save the document.
➢ Is the PDFNet .dll saving a document anywhere to the hard drive?
E.g. If I were to set a
➢ PDFDoc with a stream or byte array, will a copy (in any form) be
saved to the user’s
➢ hard drive, or will it ever be possible to access that document from
the user’s hard drive?
PDFNet does not use any temporary files or disc access when reading
or viewing documents loaded from a memory buffer.
To keep memory under control during PDF generation or editing, PDFNet
is (by default) caching some data on disk. To disable this behaviour
and store everything in memory even during generation or editing,
simply call PDFNet.SetDefaultDiskCachingEnabled(false).