Handling large binary data transfers
See original GitHub issueFor example, you might have an HTTP endpoint for uploading images. Typically, this would be handled with a multipart/form-data
request. What would be the best way to handle this with an OpenRPC API?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Sending and Receiving Binary Data - Web APIs | MDN
This is building a 512-byte array of 8-bit integers and sending it; you can use any binary data you'd like, of course. Submitting...
Read more >What is a good way to write/read large binary data to/from file?
I think it starts reading from begining of file again instead of where it left off. That's actually correct, given that the code...
Read more >Transfer very large binary data table from one Sql Server to ...
Hello,. we have 2 sql server nodes. On one of the nodes, there is a table with a varbinary(MAX) column. we need to...
Read more >Handling Binary Data in SOAP with MTOM - DZone
In this article, we discuss how to handle binary data in SOAP with MTOM in order to significantly reduce file size.
Read more >3.5. Large Message Transfers - Learning WCF [Book] - O'Reilly
Large Message Transfers Transferring large amounts of data between clients and services requires forethought. When messages are text encoded, large binary ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @BelfordZ, I had similar thoughts. Here are my ideas in another issue: https://github.com/kbaseIncubator/jsonrpcbase/issues/20
In the issue, I mention leaning towards the CBOR/BSON way, because it keeps the transport agnosticism. But I’m still not crazy about it because I think it’d be pretty tricky to stream only one nested param to a file without loading the whole payload into memory.
I feel like the multi-part way would be easier to stream the binary data to a file, without the surrounding json structure, and that seems important. But it would be HTTP-specific.
I do realize this is not the responsibility of the Open-RPC layer, but is more of a tangential problem. Feel free to close if you’d like.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.