You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see a test that requests a token valid for 24 hours, then checks that the token does indeed expire the following day 24 hours later (or within a minute of that).
The text was updated successfully, but these errors were encountered:
The type of ARTAuthTokenParams.ttl is NSTimeInterval:
Used to specify a time interval, in seconds.
I don't think that in itself is wrong, especially if that is a standard type, but we do need to ensure then that all serialisation to and from JSON / MsgPack when communicating with Ably is converted correctly
it yields sub-millisecond precision over a range of 10,000 years.
So there's no problem with precision here. (TK2a is kind of fuzzy about it, though, because it says that it is "in milliseconds" but then specifies the type as "long", so it doesn't define to what extent times smaller than a millisecond should be significative; anyway, the milliseconds requirement is met by NSTimeInterval.)
I agree with @mattheworiordan. Translating to iOS' standards is mostly what we're doing all around.
The type of
ARTAuthTokenParams.ttl
is NSTimeInterval:I often use
uint64_t
type when I want to represent milliseconds. Some references: Precise timing measurementsReference:
TK2a
Tasks
changettl
typecheckARTDefault.ttl
as wellcheck RSA5check RSA9eThe text was updated successfully, but these errors were encountered: