Hey James, There's no 'canonical' behavior here - it's up to the application to define the semantics they want. Absent any application-specific knowledge, there's no order imposed by Flight. So I would agree, though it could make sense for an application to tag the endpoints with some ordering instead of funneling it all through one endpoint (e.g. if the data is partitioned).
-David On Tue, Jul 27, 2021, at 13:01, James Duong wrote: > Hi, > > In getFlightInfo(), the FlightProducer is supposed to return an iterable of > endpoints that the client can retrieve data from using doGet(). > > What's not really clear to me is if the order of the endpoints is > significant. My assumption is that the order is not significant -- the > client should be able to retrieve from any endpoint in any order (and do so > concurrently) without having to order the data at the end. If the order of > the data is significant, I'd expect the producer to just return one > endpoint with data in the correct order. > > Is this the case? > > -- > > *James Duong* > Lead Software Developer > Bit Quill Technologies Inc. > Direct: +1.604.562.6082 | jam...@bitquilltech.com > https://www.bitquilltech.com > > This email message is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. Any unauthorized review, > use, disclosure, or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply email and destroy > all copies of the original message. Thank you. >