Hello Arrow developers I’m exploring the use of RecordBatchStreamWriter and RecordBatchStreamReader to serialize/deserialize Arrow data, over HTTP, as binary data payload. My assumption is that these methods provide a machine-independent serialization mechanism, allowing the Arrow format over HTTP to serve as a reliable and efficient protocol for data exchange between client and server.
Few questions: 1. Can I depend on these interfaces to leverage Arrow format as binary exchange mechanism over HTTP? 2. Are there any limitations or considerations I should be aware of when adopting this approach for such use cases? 3. Is there a standardization in place for compatibility as clients machines may update arrow library independently (example client using arrow version 19 for StreamReader while the server is using version 18 for StreamWriter). Your insights and advice would be greatly appreciated. Thanks Amarinder S Randhawa
