This commit is contained in:
Felipe Lessa 2015-05-26 02:50:05 -03:00
parent 3a56d222a8
commit 42e42f7f42

View File

@ -28,11 +28,11 @@ to be paired up with two companion packages:
* _Frontend_, bindings for your web framework of choice. * _Frontend_, bindings for your web framework of choice.
Currently we support: Currently we support:
* `serversession-frontend-yesod`: Support the Yesod * `serversession-frontend-yesod`: Support for the Yesod
framework. Replaces the default `clientsession`. framework. Replaces the default `clientsession`.
* `serversession-frontend-snap`: Support the Snap framework. * `serversession-frontend-snap`: Support for the Snap
Replaces the default framework. Replaces the default
`Snap.Snaplet.Session.Backends.CookieSession` based on `Snap.Snaplet.Session.Backends.CookieSession` based on
`clientsession`. `clientsession`.
@ -96,7 +96,7 @@ though, please bear in mind that:
backends. backends.
* There's no way of setting timeouts and cookie persistence on * There's no way of setting timeouts and cookie persistence on
a per-session basis, only a global basis. a per-session basis, only on a global basis.
## Background ## Background
@ -121,7 +121,7 @@ However, there are some disadvantages to client-side sessions:
to maintain long expiration times while still having secure to maintain long expiration times while still having secure
logouts. logouts.
* _Cookie size_. As the cookie contain the whole session data * _Cookie size_. As the cookie contains the whole session data
plus some overhead, care must be taken not to create too much plus some overhead, care must be taken not to create too much
session data. Yesod already saves the logged in user ID via session data. Yesod already saves the logged in user ID via
`yesod-auth` and a XSRF token via `yesod-form`. This `yesod-auth` and a XSRF token via `yesod-form`. This