Return-Path: Mailing-List: contact modperl-help@apache.org; run by ezmlm Delivered-To: mailing list modperl@apache.org Received: (qmail 80805 invoked from network); 2 Jun 2000 00:07:49 -0000 Received: from unknown (HELO pharkins.office.etoys.com) (206.160.168.2) by locus.apache.org with SMTP; 2 Jun 2000 00:07:49 -0000 Received: from localhost (pharkins@localhost) by pharkins.office.etoys.com (8.9.3/8.9.3) with ESMTP id RAA10233; Thu, 1 Jun 2000 17:12:28 -0700 X-Authentication-Warning: pharkins.office.etoys.com: pharkins owned process doing -bs Date: Thu, 1 Jun 2000 17:12:28 -0700 (PDT) From: Perrin Harkins X-Sender: pharkins@pharkins.office.etoys.com Reply-To: Perrin Harkins To: Niral Trivedi cc: modperl@apache.org Subject: Re: Apache::Session In-Reply-To: <3936C026.81E9EEE2@planet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 1 Jun 2000, Niral Trivedi wrote: > Now, only way to remove this information from backing store is to do > 'tied(%session_hash)->delete', Am I right? I mean is there any way we > can remove these entries by setting 'time_out_interval' or something > like that?? Your cron job idea sounds fine. If you need the expiration to be more precise than that, you could alter the storage class you're using to check a timeout value in the session against the current time. If the session is too old, it acts like it couldn't find it. In the database classes this could be done as a WHERE clause in the SQL. You'd still want to run a cron to actually delete the old session data. - Perrin