Rendering |
| Member name | Value | Description |
|---|---|---|
| Chromium | 3 | The Chromium rendering engine, run on this machine from the native package installed with the application. |
| ChromiumRemote | 4 | The Chromium engine and the PDF tools, run by a remote ExpertPdf engine (the expertpdf/engine container image) over HTTP. The engine is addressed by EngineEndpoint and, when it requires one, EngineAccessToken. |
Chromium runs the engine on the machine the application runs on, from the native package installed with the application. ChromiumRemote sends the work over HTTP to a remote ExpertPdf engine, which ships as the expertpdf/engine container image and can run on another machine, in another container or beside the application in the same pod. The application then needs no native package, which is how the library runs on Alpine Linux (where the native engines cannot run) and how an application keeps its own image small.
RenderingEngine is the default for every converter and the only setting the PDF tools read. A converter can override it for its own conversions through its RenderingEngine property. The value of Chromium is the one the earlier ExpertPdf libraries gave it, so code that selects it compiles unchanged.