[Seaside] Handling expired Session in Seaside 3.0

[Julian Fitzell]

Well, you don't need a session to render a component. It's just a
renderable object so you could hand it to a Builder to generate
content.

I'm not *sure* that's better than another kind of object, but it does
seem to be what people ask for and in the case where you just want to
render something, it does seem logical enough.

Julian


On Wed, Nov 3, 2010 at 9:18 AM, Johan Brichau <johan at inceptive.be> wrote:
> Hi Julian,
>
> Wouldn't a full component lead to a circular problem involving expired sessions for that component?
>
> I guess a handler like an error handler would do the job, no?
>
> On 03 Nov 2010, at 09:43, Julian Fitzell wrote:
>
>> This is a common request... it might be nice to extend the
>> Application's configuration so you can specify, as well as a root
>> component, a component to be used in case of an expired session.
>> Anyone have thoughts?
>>
>> Julian
>>
>> On Wed, Nov 3, 2010 at 7:35 AM, Johan Brichau <johan at inceptive.be> wrote:
>>> Udo,
>>>
>>> As far as I know, you would need to create a specific subclass of WAApplication and override #handleExpired: to do what you want.
>>> Then use that specific subclass to register your main component as an application (the standard WAAdmin>>register:asApplicationAt: uses WAApplication)
>>>
>>> Overriding #initialRequest: on your initial component might be of help to know if the request was for an expired session. But you probably need to pass some info in the request in the #handleExpired: method.
>>>
>>> Now, this is all theory, I have no experience doing that myself ;-)
>>> Let us know if you succeed.
>>>
>>> Johan
>>>
>>> On 02 Nov 2010, at 21:41, Udo Schneider wrote:
>>>
>>>> All,
>>>>
>>>> if this is just an RTFM question I'm happy to read on my own ... however I'm searching for a solution to handle expired sessions in Seaside 3.0. My goal is to either display a specific component when a request for an expired session is recieved or to be able to find out if a request was for an expired session in my initial component.
>>>>
>>>> Any pointers?
>>>>
>>>> CU,
>>>>
>>>> Udo
>>>>
>>>> _______________________________________________
>>>> seaside mailing list
>>>> seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>>> _______________________________________________
>>> seaside mailing list
>>> seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>