I already discussed this topic with Jack by e-mail but still will add it as a feature request in the forum (for HtmlToPdf).
It's about overriding the normal HTTP-Handler for object retrieval. I.e. we are serving objects internally from an archive system. What we would like to achieve is to have a boxed rendition service that does not need an IIS installation (or some other webserver installation). Basically we would like to omit the HTTP-Stack.
What we would like to be able is to do something like:
Code: C#
EOHttpResponse HandleRequest(EOHttpRequest) {
...
return result;
}
HtmlToPdfOptions.HttpHandler = HandleRequest;
with EOHttpRequest and EOHttpResponse being simple objects that contain all relevant information to feed the browser (HTTP Header, HTTP Body).
Instead of retrieving objects over HTTP EO would then simply use the HandleRequest method provided to gather the page objects (css, jpg, etc.). This would allow for completely webserver-less processing of HTML-Renditions.
In our case where we control the serving application as well as the renditioner process we have much more control over the whole process. This helps for verification (if everything went well - very important in litigation scenarios), faster processing (no HTTP stack/webserver involved, less overhead), better control (number of database connections use, filtering of irrelevant requests, etc.).