Add support for third party session handlers #137
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a constructor option
sessionHandler
which provides a hook for third party developers to implement their own session stores (e.g. using Redis or something).The default session handler, from
src/sessions.coffee
implements the in-memory store that RiveScript previously used. All internal code references to user variables fromRiveScript._users
have been modified to go through the publicsetUservar()
function and friends. These functions then delegate to the equivalent functions from the session handler. The core RiveScript library provides no other session handlers, but some may be added as examples in theeg/
directory in the future.Session handlers aren't required to implement all functions (the unit test tries setting a "null" session handler which gives the bot really bad amnesia).
Fixes #135