Received: by 10.220.200.76 with SMTP id ev12mr147645vcb.15.1298235819091;
        Sun, 20 Feb 2011 13:03:39 -0800 (PST)
X-BeenThere: silverstripe-dev@googlegroups.com
Received: by 10.220.109.143 with SMTP id j15ls1157439vcp.1.p; Sun, 20 Feb 2011
 13:03:38 -0800 (PST)
Received: by 10.220.187.134 with SMTP id cw6mr155366vcb.6.1298235818232;
        Sun, 20 Feb 2011 13:03:38 -0800 (PST)
Received: by 10.220.187.134 with SMTP id cw6mr155365vcb.6.1298235818212;
        Sun, 20 Feb 2011 13:03:38 -0800 (PST)
Return-Path: <s...@silverstripe.com>
Received: from mail-vx0-f180.google.com ([209.85.220.180])
        by gmr-mx.google.com with ESMTPS id t10si727545vcc.3.2011.02.20.13.03.37
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 20 Feb 2011 13:03:37 -0800 (PST)
Received-SPF: pass (google.com: domain of s...@silverstripe.com designates 209.85.220.180 as permitted sender) client-ip=209.85.220.180;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of s...@silverstripe.com designates 209.85.220.180 as permitted sender) smtp.mail=...@silverstripe.com
Received: by vxc38 with SMTP id 38so416638vxc.11
        for <silverstripe-dev@googlegroups.com>; Sun, 20 Feb 2011 13:03:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.194.73 with SMTP id dx9mr123110vcb.163.1298235817349; Sun,
 20 Feb 2011 13:03:37 -0800 (PST)
Received: by 10.220.176.71 with HTTP; Sun, 20 Feb 2011 13:03:37 -0800 (PST)
In-Reply-To: <36909F31-F18B-4FDC-BA8D-F948A5A51B71@silverstripe.com>
References: <16123856.504.1298210834682.JavaMail.geo-discussion-forums@yqq19>
	<1226d762-3f70-42cc-9e7a-adb06cb7b0ce@w9g2000prg.googlegroups.com>
	<AANLkTinUpNw48XKuvde3p=FZKveGkQYQuTEZzYsYCOkC@mail.gmail.com>
	<AANLkTim-PofTm0V+-=j_r6R4F0JkzJtfUMXh9wmr4vf7@mail.gmail.com>
	<36909F31-F18B-4FDC-BA8D-F948A5A51B71@silverstripe.com>
Date: Mon, 21 Feb 2011 10:03:37 +1300
Message-ID: <AANLkTimYtpHb0QV2HSt0R10HrdwOO+tUYoFNv8_tNAqA@mail.gmail.com>
Subject: Re: [silverstripe-dev] Re: File overhaul
From: =?ISO-8859-1?Q?Sam_Minn=E9e?= <s...@silverstripe.com>
To: silverstripe-dev@googlegroups.com
Content-Type: multipart/alternative; boundary=90e6ba53ab44ba5436049cbd14fa

--90e6ba53ab44ba5436049cbd14fa
Content-Type: text/plain; charset=ISO-8859-1

>
> Tim: Why doesn't decoration of the File class work for you,
> rather than subclassing? BTW: When I first read the "handler" API
> suggestion I thought
> it had something to do with HTTP request handling, so got a bit confused :)
>

I think that the idea of a registration API could be a good one - we don't
need to resort to decorators for every single API design challenge.

However, the most important question hasn't yet been answered: what is the
registered handler going to do?

--90e6ba53ab44ba5436049cbd14fa
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"wo=
rd-wrap:break-word">Tim: Why doesn&#39;t decoration of the File class work =
for you,<div>
rather than subclassing?=A0BTW: When I first read the &quot;handler&quot; A=
PI suggestion I thought<div>it had something to do with HTTP request handli=
ng, so got a bit confused :)</div></div></div></blockquote><div><br></div>
<div>I think that the idea of a registration API could be a good one - we d=
on&#39;t need to resort to decorators for every single API design challenge=
.</div><div><br></div><div>However, the most important question hasn&#39;t =
yet been answered: what is the registered handler going to do?</div>
</div>

--90e6ba53ab44ba5436049cbd14fa--