Add skew tolerance to time based constraints
Description
It is somewhat difficult to keep time in sync in distributed systems. Picking a (lets say "now at the wall clock") time at the client (which could be a browser that we have no control over) and instantly sending it to the backend can easily cause constraint validation for Future/FutureOrPresent constraint violations in one or Past/PastOrPresent constraint violations in the other direction. It would be nice if it would be possible to specify a skewTolerance-Duration as optional parameter for time based constraints or as a global validator property/ or property of the clock provider.
What do you think about something like?
1
@FutureOrPresent(skewTolerance=@Tolerance(amount=5, unit=TimeUnit.SECONDS))Environment
None
Status
Assignee
Unassigned
Reporter
Daniel Wegener
Labels
None
Worked in
None
Feedback Requested
None
Feedback Requested By
None
backPortable
None
Community Help Wanted
None
Suitable for new contributors
None
Requires Release Note
None
Pull Request
None
backportDecision
None
backportReEvaluate
None
Priority
Major