On Thu, Aug 23, 2012 at 11:10 PM, Mike Orr <[email protected]> wrote: > I need to share sessions between an existing Pylons site and a new > mobile-site derivative that's a subdomain (example.com and > m.example.com). So I need to share the session cookie and session > store. In the Beaker docs it says that > session.domain = .domain.com > will make the cookie shared across subdomains. That leaves the session > store. I'm using the default file-based sessions. If I just point the > two applications to the same session directory, will they do locking > properly?
If everything runs on a single server, I guess you can use file-based sessions. If you want more flexibility, or want to avoid filesystem access, you might want to look at Redis-backed sessions using beaker_extensions. -- Ronan Amicel «« Twitter overload? »» Get your daily summary at http://focus.io/ -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
