"Jeffrey W. Baker" wrote:
>
> On Fri, 28 Apr 2000, Dan McCormick wrote:
>
> > "Jeffrey W. Baker" wrote:
> > >
> > > On my sites I use a central database for storing the session objects, and
> > > all of the https servers access this central resource. Obviously if it
> > > goes down, everything is toast, but the same can be said of the database
> > > that stores all of the customer information, etc.
> > >
> > > -jwb
> >
> > Are you using Apache::ASP to generate sessions?
> >
> > Has anyone tried using Tie::DBI to store Apache::ASP sessions in a db?
> > That might solve problems with NFS sharing issues, though it might also
> > bog things down.
>
> No, I use Apache::Session - jwb
Dan,
I suggest you switch to Apache::Session. If you've got a site that gets
heavy traffic (which sounds like is the case if you're thinking about load
balancing), you definitely want a true DBMS handling your session data, not
just a Berkeley DB_File.
I used to use Apache::ASP for session management but switched to
Apache::Session for this reason. I think Apache::ASP is a great solution
for low-traffic sites, but Apache::Session is a must for high-volume and/or
load-balanced sites.
Apache::Session incorporates its own Tie::DBI implementation to manage
sessions. (is this correct, Jeffrey?) I don't know how successful you'd be
taking a hash already tied to a DB_File (via Apache::ASP) and then trying to
tie it to a DBMS via Tie::DBI. At best, you'd have two copies of your
session data, but most likely it wouldn't work.
-Adi
