ab
It is indeed not yet supported. But it is planned in the close future, with the upcoming proxy and reverse proxy features of our async server. We need this, because...
Note that all the internal logic for using a TStream instead of a RawByteString is already there. We just need a mean to trigger it properly. Perhaps in OnBeforeBody or...
My guess is that our `TStream` support should be separated from mullti-part decoding, because - Huge content could be sent without multi-part, but e.g. with or without chunking - A...
Yes, the `TStream` would be a file, either with a name supplied by the callback, or a temporary name.
Currently looking into that. It sounds like if we could have chunked + multipart. https://stackoverflow.com/questions/13969403/chunked-transfer-and-multipart-http So since we already have chunked support with a destination TStream, I will need to...
Update: Why is this not merged yet? We have merged a lot of fixes from third parties, and it almost every time broke the code working for other users of...
DId you enable Uniscribe rendering in SynPDF?
Update: Why is this not merged yet? We have merged a lot of fixes from third parties, and it almost every time broke the code working for other users of...
Update: Why is this not merged yet? We have merged a lot of fixes from third parties, and it almost every time broke the code working for other users of...
Thanks a lot for the interest! Perhaps also worth adding the existing pdf tests of mORMot 1. Also, ensure your code compiles with FPC, and has no warning. Your usage...