[Seaside-dev] expiry policies

Philippe Marschall philippe.marschall at gmail.com
Thu Sep 18 06:19:29 UTC 2008


2008/9/17 Julian Fitzell <jfitzell at gmail.com>:
> On Wed, Sep 17, 2008 at 8:59 PM, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
>> WAExpiringHandler >> #handleRequest:
>>
>> self isActive ifFalse: [ ^ self policy expiredResponseForContext:
>> aRequestContext ].
>>
>>
>> Why do we have that in the policy which might or might not be a
>> WAExpiredExpiryHandler? Why not in the response factory?
>
> Well, I thought that the policy might want to give a more detailed
> error message about why it had expired and so on. But perhaps that is
> misguided... I don't feel strongly about it and could certainly put it
> back to "self responseFactory pageExpiredFor: aRequestContext".

I think you'll rather have an application specific error with the look
and feel of your application.

Cheers
Philippe


More information about the seaside-dev mailing list