Received: by 10.151.154.8 with SMTP id g8mr3525378ybo.26.1244837210453;
        Fri, 12 Jun 2009 13:06:50 -0700 (PDT)
Return-Path: <pligh...@gmail.com>
Received: from yw-out-1718.google.com (yw-out-1718.google.com [74.125.46.152])
        by gmr-mx.google.com with ESMTP id 14si233019gxk.3.2009.06.12.13.06.49;
        Fri, 12 Jun 2009 13:06:49 -0700 (PDT)
Received-SPF: pass (google.com: domain of pligh...@gmail.com designates 74.125.46.152 as permitted sender) client-ip=74.125.46.152;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of pligh...@gmail.com designates 74.125.46.152 as permitted sender) smtp.mail=pligh...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by yw-out-1718.google.com with SMTP id 6so1218376ywa.28
        for <sitemesh-team@googlegroups.com>; Fri, 12 Jun 2009 13:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:sender:received:in-reply-to
         :references:date:x-google-sender-auth:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        bh=j/UelIax8/cE7h7o+cRV3C028Qjq5kpUwGNYplWYeIU=;
        b=TQ8KCG28NznqQQfeOYftY27P6TN6sBaueZdO1klfX15kAoNCq8nZUZDN08qjWAMl7W
         zed0aHL0gAtzHeiOK0/9qXrl4SZ7Bdi5/y4u48iwOef/F04XHZvuEozniemPde0xGd3V
         KlWIxPeKGPy070G38xsxemAeusfdUaDj45DZ0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=BmmSH1qyvf4M5ch5IqQoc3kd1gbsxIL2PLDYGgVMCXv+RnJE7M1U5dTgS9/Rn2g/ua
         ddtCkrgXEV66R7QxiMgJKqx7ohj8slALStsxMvJ2V0JI1rNZtrBLWLxXrM58Q8AMO9Wa
         Ckp5J2Ub2MveW1ft3OK4IddKDHBu9r6nrudYE=
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Sender: pligh...@gmail.com
Received: by 10.100.229.14 with SMTP id b14mr5355790anh.187.1244837209251; 
	Fri, 12 Jun 2009 13:06:49 -0700 (PDT)
In-Reply-To: <81d74db5-2e28-450a-b5cb-ba6226187...@r33g2000yqn.googlegroups.com>
References: <81d74db5-2e28-450a-b5cb-ba6226187...@r33g2000yqn.googlegroups.com>
Date: Fri, 12 Jun 2009 13:06:49 -0700
Message-ID: <c372afa40906121306y22e2aecdhbf35b514e6b85...@mail.gmail.com>
Subject: Re: [SiteMesh-Team] Naming convention for different types of Filters
From: Patrick Lightbody <patr...@lightbody.net>
To: sitemesh-team@googlegroups.com

No big ideas here, but I'd say keep the "default" one named simple...
like just SiteMeshFilter.

Patrick

On Fri, Jun 12, 2009 at 1:02 PM, Joe Walnes<joe.wal...@gmail.com> wrote:
>
> I need a break from reviewing logos. Back to the never ending config
> stuff...
>
> Because we want to give users the choice of how to configure SiteMesh
> (e.g. programatically, via XML, <init-params>, Spring,
> convention....), WITHOUT making it too confusing or adding too many
> layers of indirection/factories/providers, I've ended up with a
> different set of top-level Servlet Filters.
>
> But I'm struggling to come up with sane names for the filters.
>
> What I have at the moment:
> =A0org.sitemesh.config.xml.XmlConfiguredSiteMeshFilter
> =A0org.sitemesh.config.properties.InitParamConfiguredSiteMeshFilter
> =A0org.sitemesh.config.spring.SpringConfiguredSiteMeshFilter
> =A0...etc...
>
> Looks a bit scary. Any suggestions for how to simplify the names, yet
> have them meaningful?
>
> -Joe
>
> >
>