You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have three DoExchange calls, subscribe, snapshot, and publish. While our app_metadata contents (BarrageMessageWrapper) already disambiguate as to what the stream will be for, FlightClient assumes that the initial FlightData consists only of a FlightDescriptor, and allows no other data to be passed by the client to the server.
While this initial message isn't necessary for deephaven clients, it would be nice to make it easy for flight clients to call these services in a consistent way.
The text was updated successfully, but these errors were encountered:
We have three DoExchange calls, subscribe, snapshot, and publish. While our app_metadata contents (BarrageMessageWrapper) already disambiguate as to what the stream will be for, FlightClient assumes that the initial FlightData consists only of a FlightDescriptor, and allows no other data to be passed by the client to the server.
While this initial message isn't necessary for deephaven clients, it would be nice to make it easy for flight clients to call these services in a consistent way.
The text was updated successfully, but these errors were encountered: