-
Type:
Task
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: evergreen
-
None
-
Evergreen - Milestone 1
From this thread on a JEP
Another route that comes to mind for me: don't tell the client anything if their latest update level is tainted already, for example:
Compute the update level for the client
Consult the tainted table
If the update level exist in the tainted level, return a 304 Not Modified back to the client.
I think we'll just need another model, and another service for this. Not much complex.