Yes, that sounds about right to me.
I'd like getStream to return Future or something like that,
additionally. That way we could free up the RPC handler thread.
Metadata would need some work, so possibly ArrowReader isn't the right
interface, but something like it. (This is more a sketch of an i
Hi David,
Thanks so much for the fast reply, that’s really helpful context.
I like the idea you mentioned where the application provides an ArrowReader.
Would that story go something like the following?
1. Today in FlightService doGetCustom, a GetListener is passed to
producer.getStream - this
Hi Nate,
That sounds about right to me (it's been a while since I've dug into gRPC-Java
behavior). A better server API is something I've long wanted to consider and
haven't had the time to; the current APIs try to let you write
blocking/procedural code as much as possible which then does not me
Hello,
I'm hoping to check my understanding around various ways to implement a
DoGet handler with respect to flow control, and then inquire about
potential future API changes.
First, I'm aware of 3 ways to respect flow control when implementing a Java
server's DoGet that have different characteri
