This is an automated email from the ASF dual-hosted git repository.
ianmcook pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-experiments.git
The following commit(s) were added to refs/heads/main by this push:
new 5657432 Improve get_simple README (#15)
5657432 is described below
commit 565743255a33ddbfdb8509886ab2f84fd9bb6c87
Author: Ian Cook <[email protected]>
AuthorDate: Mon Mar 11 00:29:52 2024 -0400
Improve get_simple README (#15)
---
http/get_simple/README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/http/get_simple/README.md b/http/get_simple/README.md
index e641b0c..5f9c552 100644
--- a/http/get_simple/README.md
+++ b/http/get_simple/README.md
@@ -25,6 +25,8 @@ This directory contains a set of minimal examples of HTTP
clients and servers im
The examples here assume that the server cannot determine the exact length in
bytes of the full Arrow IPC stream before sending it, so they cannot set the
`Content-Length` header or serve Range requests.
+The client examples here assume that the client needs to hold the full
received data in memory in an Arrow data structure for further in-memory
processing. (The case in which the client simply writes the result directly to
a file is much simpler and can be achieved trivially by using
[curl](https://curl.se) or similar.)
+
To enable performance comparisons to Arrow Flight RPC, the server examples
generate the data in exactly the same way as in
[`flight_benchmark.cc`](https://github.com/apache/arrow/blob/7346bdffbdca36492089f6160534bfa2b81bad90/cpp/src/arrow/flight/flight_benchmark.cc#L194-L245)
as cited in the [original blog post introducing Flight
RPC](https://arrow.apache.org/blog/2019/10/13/introducing-arrow-flight/). But
note that Flight example sends four concurrent streams.
If you are collaborating on the set of examples in this directory, please
follow these guidelines:
