On 04/16/2015 07:35 AM, Attila Bárdi wrote:
> If you have multiple instances running or your app is behind a load balancer
> on different hosts then you really need a caching system.
> If you use only one instance then the cookie is fine.
Well, the browser of the user will pass the cookie to the instance so you
actually don't need to cache it on your server.
That is the beauty of the cookie approach.
Regards
Racke
>
> On Thu, Apr 16, 2015 at 7:32 AM, Yitzchak Scott-Thoennes <[email protected]
> <mailto:[email protected]>> wrote:
>
> On Wed, Apr 15, 2015 at 3:16 PM, Andrew Solomon <[email protected]
> <mailto:[email protected]>> wrote:
>
> Bill,
>
> Once a website with cookies is in production it needs caching systems
> like Memcached or Redis for key-value data storage where you can access the
> data from different processes.
>
>
> Dancer::Session::Cookie doesn't use a backend at all; the session data is
> entirely stored in the (encrypted, signed) cookie. There are obvious
> downsides to this, but not the ones you mention.
>
>
> _______________________________________________
> dancer-users mailing list
> [email protected] <mailto:[email protected]>
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>
>
>
>
> _______________________________________________
> dancer-users mailing list
> [email protected]
> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
>
--
Modern Perl, Dancer and eCommerce consulting.
_______________________________________________
dancer-users mailing list
[email protected]
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
