Sessions are, in many bits of web software, used to store the details of the currently logged in user, and to provide the concept of a user being logged in and logged out. Known is no exception in this.
These sessions need to be stored, in some way, on the server. Usually this is either stored in files, or in a database.
Known currently has the ability to store sessions in the currently enabled database engine (Mysql, mongo etc), or in files. However, for various reasons (e.g. you want to use a different database engine to store sessions, or you want to implement a fancy session store), it would be useful to decouple the sessions from the database.
This pull request adds the ability to specify, in your
config.ini, a handler class implementing the
This new class can then implement a session handler which uses a different storage engine, other than just files and the current database.