Commits on Nov 5, 2020

1. Clarify trips and status changes response behavior …

   In MDS 0.4.x we request trips and status changes for a given hour.
   A provider may have no data to report for the requested hour
   multiple reasons, including:
   
   - The hour has not yet fully passed
   - The provider was not operational in the region during the hour
   - The provider has not yet completed processing that hour's data
   - No trips or events occurred during the hour
   
   Differentiating the last two reasons is particularly important because
   it lets consumers of APIs know whether or not they need to re-request
   the hour at a later time. A successful 200 response with an empty
   list of data clearly communicates that the provider has nothing to
   report for that hour and that it's not necessary to try again later.
   Having this behavior consistent across providers would help us at
   Populus spend less time requesting data and reduce the number of
   requests received by providers.

   

   jiffyclub committed Nov 5, 2020
   Configuration menu

   • View commit details
   • Copy full SHA for b07bb80
   • Browse repository at this point

   Copy the full SHA

   b07bb80 View commit details

   Browse the repository at this point in the history