Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Reasoning:
- We reuse the Routing Context as an optimization on the ServerSession.
- By the time the Routing is done, we will process the references on a IO callback.
- if anyone used any state in between the Routing and Storage, you could have an invalid operation.
We were lucky that the method processReferences in PostOffice was pretty much static and no actual bug happened because of that, however I almost thought we had something scary going on.
So, to avoid this kind of issue ever being introduced in the codebase I am moving the processReferences away from RoutingContext.
Attachments
Issue Links
- links to