On Fri, Sep 18, 2009 at 10:51 AM, Michael Peters <mpet...@plusthree.com>wrote:
> On 09/18/2009 11:15 AM, James Smith wrote: > > But cookies are in general not big enough to store the information that >> a user would store on a website! >> > > I'm not talking about eliminating a permanent data store for your users. > I'm talking about replacing the session specific things. How much session > specific data do you really need to store? If it's bigger than 4K per-user > than yes you can't use a single cookie. But like I said before, the > situations that you really need more than that for *session specific* data > are pretty rare. > In my case, in almost all instances, the only thing I would want to store is authenticated userid. But I cannot exclude other possibilities. Right now I use Apache::Session to store a hash in a mysql table "sessions". I have a "users" table that holds their profile information such as their email, their picture, etc. If I can find a way to set that cookie after the request is processed, I would be very happy. I can _probably_ work around it and set cookie before doing start_html, but I would prefer not to. Regarding another comment on using templates, etc: I have basically a homegrown CMS on algebra.com. And I do support templates: the presentation is mostly decoupled from content, such as where ads are places, how navigation aids are presented etc, is all decoupled. I can work on the new template for a month and the users will not notice as they will see the old template. But I like what I have as it is my own. Igor
