ianmcook commented on PR #35: URL: https://github.com/apache/arrow-experiments/pull/35#issuecomment-2354333168
@felipecrv thanks — that all sounds good. > This is still a merit of the IPC buffer compression since Python might be present on both client and server. Agreed. I think we only need to warn developers away from it when they don't control the application on the other end of the connection. (For example, if you're a SaaS service adding an Arrow-over-HTTP protocol.) Another issue to consider is that if you are caching results in Arrow format and serving them to HTTP clients as opaque binary data, and you need to make this work with the lowest-common-denominator Arrow client library, then IPC buffer compression is a poor option for you. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
