There are some problems with the implementation of external session storage:
Storing (some types?) of complex variables throws a hidden exception.
Once this happens, all subsequent external session storage (of even simple variables) fails for that session. (If one waits a while, i.e., lets the session idle for a while, the behavior seems to return to normal for simple variable storage.)
This breaks our round-robin clustering.
When the problem is elicited, we get exceptions in the `scope.log`:
This was discovered after we noticed FW/1's `redirect(..., preserve="all")` function was preserving some (large Mura) components from the RC scope in our Mura app, since we use Mura plugins (which use Mura’s murafw/1 plugin template).