Drafty thoughts on session data structures and storage

[Tom Zeller]

> New page broken off from the original page combining Authentication and
> Sessions:
>
> https://wiki.shibboleth.net/confluence/display/IDP30/Sessions
>
> This is a brain dump mostly but contains a proposal I think will work to
> map the data and lookup requirements around sessions to the storage API,
> in mostly similar fashion to what the SP does now.

I only have two superficial comments as of now.

A naming question, why "Service" in ServiceSession ? In IdPv3 a
Service is a configurable Component, a generic thing, and I was
expecting ClientSession or RelyingPartySession.

Why store the flow ID ? I think flow IDs might change, via
configuration, during a session lifetime.