A SeedLink time window request that starts in the future is accepted and then the next arriving/available data is sent to the client. Unlike the end time criteria, the start time criteria is not used to filter data out of the request, but only to set the initial buffer position.
Possible solutions:
Do not accept future time window requests, return an error when submitted
Filter the data on the start time criteria
Leaning towards the first solution as I cannot think of legitimate use cases for future time window requests and it's easier and cleaner to implement.
A SeedLink time window request that starts in the future is accepted and then the next arriving/available data is sent to the client. Unlike the end time criteria, the start time criteria is not used to filter data out of the request, but only to set the initial buffer position.
Possible solutions:
Leaning towards the first solution as I cannot think of legitimate use cases for future time window requests and it's easier and cleaner to implement.