Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of pharkins@gmail.com designates
 209.85.221.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=vsWsg6+w5kwi0MHYEJCWqRk4Uuf5OiizzzsKksSyquRuEnomg4RlX5lQp5iLM1xRkJ
         j43DkbAo9Xcz7CunUh5XKpR8CKawdNZ6rULuac6dG5vcQAcyjfFXlRXdqcqeUleTfqzq
         WomUMDZL5ueT0WJJ9jDYb+9A2uksV3oFcnGWs=
MIME-Version: 1.0
In-Reply-To: <6E362660-4E52-4CA2-83C0-9379960C5EF2@POBOX.COM>
References: <6E362660-4E52-4CA2-83C0-9379960C5EF2@POBOX.COM>
Date: Wed, 27 Jan 2010 17:45:59 -0500
Message-ID: <66887a3d1001271445u5f4d6f1dm1c0e95c058f49f7d@mail.gmail.com>
Subject: Re: writing CGI::Session sessions only when necessary
From: Perrin Harkins <pharkins@gmail.com>
To: Jonathan Swartz <SWARTZ@pobox.com>
Cc: modperl@perl.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jan 26, 2010 at 7:42 PM, Jonathan Swartz <SWARTZ@pobox.com> wrote:
> On our site we create a new CGI::Session object at the beginning of the
> request, so that it can be used anywhere in the web code.
>
> However, sessions are rarely written to, so at the end of the request I'd
> like to avoid actually writing out a new session to backing store unless a
> param actually got set.

It might be simpler to just write immediately when you set a param.
It's simple and foolproof, and it's only a negative for performance if
you normally set multiple params in a single request.

If your ultimate goal is to fix performance on your servers, I'd
recommend looking at using encrypted data in a cookie and ditching
server-side session storage.

- Perrin