When concurrant entrances to the same session occur, each editing using a different registered variable, the standard /tmp file session storage seems to be plagued with race conditions and only a few of the concurrant sessions save their variables (probably all do but the file handle's position is messed up and overwritten by the others).

Some way of locking the /tmp session file would be useful. In the meantime I suppose SQL sessions would fix things.