Hi,
We have implemented a solution with has two steps. The first call/post is with the metadata of the filedocument, the second call/post is with the contents. This was because of files up to 100mb and base64 encoding these was giving performance issues.
This is the second step (published side) where only the contents are received.
This is the first and second step (consumed side)
Second REST call:
Do a base64 encode and decode for the binary. You then transport the binary as string.
Regards,
Ronald
Implement Chunking for the document content to trasnfer via rest API user thread pool so the u can call multiple rest to trans this chuked document and reassemble the document chunks