Enables or disables sandboxing (worker process isolation).
Sub Sandboxed(newVal As Bool)
True - Enable sandboxing (default)
False - Disable sandboxing
Sandboxing is a technique that isolates the conversion functionality into a separate executable. In case the implementation crashes, it is this external process that blows up, instead of the application or server that is using the SDK. With sandboxing enabled, a corrupt or malicious PDF can't hurt the web server, because easyConverter is not running inside IIS.
The other advantage is that sandboxing enables real timeout functionality by killing the worker process after a certain amount of time.
Finally, sandboxing also increases security by isolating PDF parsing, JPEG decompression and other similarly dangerous tasks in a separate process that has no physical access to the web server's memory. For example, a zero-day vulnerability in easyConverter would only let the hackers break into the current PDF conversion, and nothing else.
With sandboxing each conversion runs in a completely independent executable.
Sandboxing is enabled by default, and it is strongly recommended that every server customer uses this feature, unless they implement their own, independent sandboxing. If sandboxing is turned off, easyConverter runs directly inside the customer's own application, which opens up a lot of vulnerability issues, and makes timing out impossible. For example, a crash in easyConverter due to a broken PDF could kill the entire Java runtime or the whole IIS worker process, unless sandboxing is enabled.
The performance hit due to sandboxing is immeasurable compared to the time it takes to execute a PDF conversion.
oConverter = CreateObject("EasyConverter.PDF2HTML.5") ' Turn off sandboxing (not recommended) oConverter.Sandboxed = False Call oConverter.ConvertToHTML(inFileName, outFileName)