Hey Matt, There are two reasons: one is we'd like to avoid exposing that we use gRPC, since a goal has been to add support for other transports besides gRPC. (That said, FlightServerOptions does include a hook to allow configuring the gRPC server manually.) Also, we wanted to avoid exposing more API surface than necessary, at least until there's a reason to expose it.
Just to clarify - are you trying to add a Flight service to a non-gRPC server, i.e. you'd like to have Flight over HTTP/1? What server framework/library are you using? -David On Wed, Nov 3, 2021, at 02:52, Matt Youill wrote: > I've noticed a lot of Flight functionality is hidden in "internal" classes. > > What's the reason for this, and is there an alternative? > > Specifically, I'd like to add Flight support to an existing HTTP server, > but it looks like I must use the server that comes with > arrow::flight::FlightServerBase, or provide my own implementations of > the internal functions. Is that correct? > > Thanks again, Matt > > >
