Reading diagrams / Topic 23 of 42
After the wrapper: the reply bar
The rule
Every reply bar stands at the same place, past the hull band. That leaves a stretch on every wrapped path between the hull's exit and the bar.
Work an entry does after its wrapper returns is drawn in that stretch: a dot for a call, a ring for a resource, a diamond for a check. A path that runs clear from the exit to its bar does nothing after the wrapper. The stretch starts at the exit, the short dark tick where each path leaves the hull: there the wrapper returns. A mark left of the exit, such as the dashed hollow socket ring where the paths split, belongs to the wrapper or to the entry's socket; a mark right of it runs after the wrapper.
This is worth checking in a review. A wrapper that is meant to cover every step of a request covers nothing that runs after it.
- Marks between the exit and the bar confirm work after the wrapper; a clear run rules it out.
policy-docs.
Loading the system map.
problemsapi. Its seventeen routes are drawn as cables: routes with the same marks share one, with a count.
Loading the system map.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.