Home/ Questions/Q 8495217
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T23:30:45+00:00

In the ServiceStack session documentation here: https://github.com/ServiceStack/ServiceStack/wiki/Sessions there is some example code that defines

  • 0

In the ServiceStack session documentation here:

https://github.com/ServiceStack/ServiceStack/wiki/Sessions

there is some example code that defines a UserSession property. I expected that the setter for the property would add the newly-created data storage object to the cache. Is that missing from this sample code? Or is there some other place the session data is added to the cache?

Also, why do we have both a sessionId and a sessionKey? Wouldn’t the latter be sufficient? And we create multiple Ids (CreateSessionIds) but only ever use one (GetSessionId)?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    SessionId is just the hashed Guid, SessionKey is the unique fully-qualified key that’s used when referencing the session in the datastore (e.g. Redis).

    There exists both transient and permanent session keys defined and the one used is specified by the ss-opt cookie and can be changed by the client at anytime.

    • 0