add different handling for feed and preload (schedule) fixtures #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A bug manifested where the SDK would not fetch the latest fixture from the API in case there were 2 back-to-back fixture changes sent by the feed wihin 1 minute.
Since we always need the latest fixture state and poll the fixture API upon receiving a fixture_change message it is useful to know whether or not the fixture getter function is invoked from a preload loop or as a response to a fixture_change.
In case the fixture getter is invoked in response to a fixture_change message, it will always result in a fixture API poll - the checking for the fixture age will be skipped.
In case we are doing a preload, the old rule will stil apply - the fixture age will be checked in the fixture.expireMap.