Draft: session: uuid based storage
This is a alternative approach to !462 (closed).
Warning: dot not test, eats sessions
The idea is to decouple session names from storage, so the concept of anonymous session can be completely removed. Using random uuid for session identifiers. This patch doesn't solve problem with session defaults and where to take them from.
Pros:
- no special new session handling
- renaming session is simply changing the string in object
- user actions are preserved (it is possible to create "new session" unlike in !462 (closed))
- can experiment with generating random names for new session
Cons:
- will require transition mechanism from old storage to new one
The main answer for me is whether this is the way forward or not.