On Fri, 2004-02-20 at 05:19, Peter Galbavy wrote: > 1) Cookieless session options; I would like to support cookieless sessions, > using URL args and/or pathinfo to carry the session IDs. Looking at both the > systems, this is a manual process (unlike Apache::ASP options). Am I > mistaken ? Is there an underlying transparent mechanism in either session > manager (or a wrapper) ?
Neither of the modules you are looking at is a complete system the way Apache::ASP is. Apache::Session is just a storage mechanism for a shared hash. I think CGI::Session goes a little further by providing some basic cookie stuff. What you probably want to look at it is a higher-level module which handles more for you. Try one of these: Apache::AuthCookieURL Apache::SessionManager > 2) The data required per session will be the typical user authentication / > preferences stuff. Perhaps some additional menu-choices etc. Not much by > volume, and not a whole lot of commerce stuff. My basic advice is to put as little in a session as you possibly can. > 3) I will be using a PostgreSQL based DB for the content management, and if > (as I hope) the capacity increases require additional backends, then having > session data in a/the DB will be useful. Both the session modules support > PostgreSQL, but does anyone have any experience of performance by these > modules in this environment ? Apache::Session performed well with Oracle. Performance with Postgres is mostly a function of how well Postgres performs. Incidentally, Apache::ASP uses MLDBM::Sync instead of Apache::Session. You could do that too if you want to, and build the URL-munging part yourself. - Perrin -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
