This repository has been archived by the owner on Jul 7, 2019. It is now read-only.
Fix if it is set to absolute time, unable to store the problem. #172
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
Fix if it is set to absolute time, unable to store the problem.
|
I don't really get the problem :( Also, the way you have changed the GetExpires to always return a relative timestamp will cause problems with expirations > 30 days. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix if it is set to absolute time, unable to store the problem.
GetExpiration(DateTime expiresAt) and
GetExpiration(TimeSpan validFor)
The meaning of the return is different, there is ambiguity.And Store(StoreMode mode, string key, object value, DateTime expiresAt) cannot be successfully stored。It's as if the data returned by GetExpiration (DateTime, expiresAt) is too large