...since users are never in any one process for very long by design the risk is smaller. You might design the interactions to be brief, but how do you actually

...since users are never in any one process for very long by design the risk is smaller. You might design the interactions to be brief, but how do you actually enforce that when you need to upgrade or reclaim resources? To make this more concrete, suppose you have a shopping cart. Sure it probably only takes most people 5 minutes to check out from start to finish, but what about the stragglers? Do you have a nice way of timing out the coroutine handler due to inactivity, and saving off state when that happens? Or do you just solve it the HN way ("Unknown or expired link," hmm what does that even mean).