i am not much of a mp hacker but as I understand it, one problem with making per-session persistent connections would be that there is no guarantee that future requests in the same apache session will be handled by the same mod_perl process. This means that any backend that provided what you are asking for would need to be shared among all the mp processes. The new request would check its session ID, then connect to the db session multiplexor and provide the session credential.
Contact me off-list if you'd like to sponsor creation of this daemon, if it hasn't been done already I could set it up. On Sat, 06 Nov 2004 17:30:35 -0500, Sundar Narasimhan <[EMAIL PROTECTED]> wrote: > Hi, I've been using Apache::Session w/ mod_perl which seems to work nicely. > But I have a question -- this seems to be mostly for data. What about say > a network connection (i.e. I'd like to have one connection per user session > to a back-end server. The db persistent connections sort of do this I > presume > but they don't seem to be per session.). > > Thoughts? (or do I have to go the tomcat/servlet route?) > > Thanks, > -Sundar > > -- > 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 > > -- David L Nicol "How cool is that?" -- Elgie -- 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