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
Currently WebSession API uses Instant for many methods. It might be good to use a type that contains timezone information it rather than the implied timezone of GMT
In the very least we need to fix the following line which uses Clock.systemDefaultZone but should use a fixed timezone (GMT) so that session times are always relative to the same time zone. Beyond that I am not convinced that we need to expose anything more than Instant. It is perfectly comparable to any other "externally created moment". Why does it need to be ZonedDateTime rather than Instant? All that matters is the time relative to session creation.
I tend to agree since the usage of ZonedDateTime in HttpHeaders is mainly driven by the fact that the time zone information is directly available in the header value we parse. Not sure that applies here, so I would be for just setting GMT fixed time zone as proposed by Rossen. Would that be ok from your point of view Rob Winch?
Rob Winch opened SPR-15675 and commented
Currently WebSession API uses Instant for many methods. It might be good to use a type that contains timezone information it rather than the implied timezone of GMT
Affects: 5.0 RC2
Issue Links:
Referenced from: commits ba3a12e
The text was updated successfully, but these errors were encountered: