, Nov 3, 2020 at 9:42 AM
> Subject: Re: Closing of Server Resources
> To: dev
>
>
> I agree with David. The client and server classes provided by the
> Flight library have always been intended as low-level tools. So the
> intent is for developers to use these to create user-faci
I agree with David. The client and server classes provided by the
Flight library have always been intended as low-level tools. So the
intent is for developers to use these to create user-facing tools that
handle the details that are particular to a certain server
implementation.
On Tue, Nov 3, 202
I think in that case, you'd give users a wrapper around a
FlightClient, and not a FlightClient directly - after all, if you have
custom server-side resources to clean up, I'd assume you'd also want
higher-level operations than what FlightClient gives directly.
Best,
David
On 11/2/20, James Duong
The concern I have about making this a custom action is that FlightClient
(in Java) is a Closeable resource already.
It's a bit unintuitive to require users to run an explicit cleanup
operation, while also automating some of the clean-up
as well. It seems error-prone.
On Fri, Oct 30, 2020 at 3:56
Do you need this beyond FlightSQL? Since any user/client interface to
a server is going to require some custom development anyway (just like
the server requires custom development), if there is a need to close
resources, it seems like this could be implemented by an action that
is specific to the p
Hi,
Carrying on from this thread:
https://mail-archives.apache.org/mod_mbox/arrow-dev/202010.mbox/%3CCAJPUwMA25jprszWEsrL2zr0xz%3DgsqdB%3D_4jP06eG8S8b5--mdg%40mail.gmail.com%3E
(apologies, as I was not a member of the list at the time of this thread
starting and am unsure if it's possible to reply
