Custom state storage

Solara makes it easy to store state/data on the server side, scoped to a kernel, using reactive variables.

However, sometimes you want to store state yourself in an external system (i.e. not Solara), and for this you can use the get_kernel_id() function to get a unique id for each kernel.

If you want to store state/data scoped to a browser session, you can use the get_session_id() function to get a unique id tied to the users browser. This can be used to store state that outlives a page refresh.

In case you want to store state/data scoped to a user, you can use a similar strategy, but use a unique identifier based on the user, instead of the session id. You can take a look at Our oauth example or the authorization example for inspiration.