By this we mean publishing the route update event. Currently the event contains a shallow route (IDs only). The listener that processes this event does roughly this:

1. Retrieve locations from repository by IDs.
2. Ask routing component for paths between visits to build the routing plan.
3. Marshall the routing plan and send it over WebSocket.

All of this currently happens on the solver thread, which is a big problem! It steals time from solver and does work that's completely unrelated to solving. If that throws an exception, solver thread dies.