On Mon, Apr 11, 2011 at 8:36 PM, Joshua Paine <[email protected]>wrote:
> That would be nice, sure, but you don't need sessions for it. A simple > cookie could handle it fine, and you wouldn't have to maintain state on > the server. E.g., there's no reason not to provide that convenience to > not-logged-in users or to anonymous logged-in users, too, except that if > you used sessions for it you could potentially end up with a lot of > temporary junk stored in your repo db to handle it. > True on all accounts (though the sessions could also be stored in an external store, as opposed to in the repo). My problem at the moment is... i've just created a CGI app framework in C, with sessions support (files, sqlite3, mysql5), and now i'm desperately looking for a real use case for it ;). -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
