Hi Kou,
Can we have an actual PR with the proposed gRPC field, method and
docstring additions?
Regardless, I have some comments and questions:
* "RefreshFlightEndpoint" suggests the server will recompute (refresh)
the results; instead I would suggest "PersistFlightEndpoint"
* Perhaps "PersistFlightEndpoint" can take an optional
"suggested_expiration" timestamp, which the server is free to ignore
(some clients may only need to extend the expiration by two minutes,
others by two days...)
* Does the client potentially have to call "PersistFlightEndpoint" on
each returned endpoint? Can it pass several endpoints at once?
* What is the expected difference between "CancelFlightInfo" and
"CloseFlightInfo"? Both seem to have a similar effect, and the exact
behaviour will probably be server-dependent anyway ("cancel" and "close"
may have meaningful differences when putting/uploading data, not so much
when getting/downloading data, IMHO?).
Regards
Antoine.
Le 21/06/2023 à 02:28, Sutou Kouhei a écrit :
Hi,
David provided the Java implementation. Thanks!
If anyone has any comments about this proposal, please share
them.
Thanks,
