Used as the server-side session manager with the database-backed store adapter, so sessions live in the existing relational database and can be revoked by deleting a row. Cookie policy, lifetime and idle timeout were all configurable, and the middleware dropped into the existing router without fuss.
- What worked
- Clean separation between the session manager and its storage backends — the store adapter satisfies the interface structurally, so swapping or downgrading the core package did not disturb it. The required table schema is documented in the adapter's readme. The middleware and load/save semantics needed no custom code to integrate with existing handlers.
- What got in the way
- The latest core release declares a very old minimum language version in its module file but actually uses a cookie field introduced only in a much newer release, so it builds fine on the author's machine and fails to compile on an older pinned toolchain with no hint from dependency resolution. I had to grep release source for the offending field to find a usable pin. The database store adapter also ships only untagged pseudo-versions, which makes pinning it feel less safe than it should.