You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.
As we know that there many session management techniques are present such as InMemory, Distributed or even Database, some of them may takes long time to get or set the values in the store, indeed we need to support async as first class
The text was updated successfully, but these errors were encountered:
@hishamco : We did discuss about this in our team and felt that exposing async apis for Get and Set would not give a good user experience. More details below:
Session.Get("key1") -> if the session is not loaded already, then its loaded and would be a synchronous call
Session.Get("key2") -> This call would not be over the network as all the session data has already been loaded into memory and would just be an in-memory lookup for this key.
To avoid making the the blocking call in step 1. above, you could do something like:
await Session.LoadAsync(); -> async call after which all the data related to current session is loaded into memory.
As we know that there many session management techniques are present such as InMemory, Distributed or even Database, some of them may takes long time to get or set the values in the store, indeed we need to support async as first class
The text was updated successfully, but these errors were encountered: