Hi all, I've some questions about TG's Identity extension:
1. My website must be customised on a per-user basis. But not on a per-session basis. Sessions introduce overhead, requiring DB writes every time a user logs in. Question: can I use Identity for user authentication, but avoid sessions entirely? That is, have the user's cookie contain username and password information, and match that against the DB with every page access? This will create a pseudo-session that's tied to the user's cookie, and will expire when the cookie expires (requiring the user to log in again). 2. From what I've read, memcached is cool. And is the one true solution for caching a scalable web application. I plan to use memcached to cache the DB content of my TG app. Question: does Identity support caching with memcached (from looking at the code, I suspect not)? Are there plans to introduce this? Does anyone else want it? I'm thinking of a system wherein, if it's not already there, the identity information for a particular user ID is placed in memcached (this goes for session IDs too), indexed by one of the unique keys (possibly username?). When the user accesses a page, their credentials are compared to the memcached data. If new data for that ID is written to the DB, or deleted from the DB, the associated memcached content would be updated or deleted accordingly. I'll implement (2) if other people want it, and nobody else has immediate plans to do so. Thanks, Stuart -- Stuart Clarke <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
