[Seaside] Re: Problems with expire in Seaside

[Avi Bryant]

Fair enough, but this is something that's likely to be done at most 
once per application...
Anyway, there's no reason the expiry page can't be easily pluggable (as 
the error page already is).  I'll take this as a request for that.  But 
I'm still interested in whether anyone has any good uses for the 
#forwarder stuff that can't be just as easily handled in the URL?

On Sep 2, 2004, at 12:36 AM, Andreas Nilsson wrote:

> Well, then I guess it's all about design goals.
> It is a lot easier to just hook up a plugin or event handler than it 
> is to override classes.
> Overriding a class just to hook up an event is a bit like the good old 
> days of GUI toolkits where you had to override buttons to make them do 
> something when clicked ;)
>
> /Adde
>
> On 2004-09-02, at 00.30, Avi Bryant wrote:
>
>>
>> On Sep 2, 2004, at 12:22 AM, Andreas Nilsson wrote:
>>
>>> Is there any way to override the expire-screen / behaviour in the 
>>> current framework?
>>> That's the only advantage i can see with the Forwarder solution.
>>
>> Sure, just subclass WAApplication and override 
>> #handleExpiredRequest:.  Changing the application class used is 
>> somewhat inconvenient, and has to be done programmatically rather 
>> than through the config app - trace through #registerAsApplication: 
>> to see how.  But shouldn't be a huge deal.
>>
>> Avi
>>
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/listinfo/seaside
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside