Custom WAApplications?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Custom WAApplications?

Boris Popov, DeepCove Labs (SNN)
What was the latest on removing #applicationClass and allowing custom
subclasses of WAApplication? I personally couldn't care less for it, but
it seems to be the only clean way of overriding #expiryPathFor: and I do
recall having this conversation before, just can't recall the
conclusion.

Thanks!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

RE: Custom WAApplications?

Boris Popov, DeepCove Labs (SNN)
Also, one small change to make it easier to manipulate URLs for expiry,
since we're moving away from String'y URLs,

WARegistry>>handleExpiredRequest: aRequest
        | url |
        aRequest isXmlHttpRequest ifTrue: [^WAResponse new forbidden].
        url := WAUrl new.
        self expiryPathFor: aRequest on: url.
        url takeServerParametersFromRequest: aRequest.
        aRequest isGet ifTrue: [aRequest fields keysAndValuesDo: [:key
:value | (url isSeasideField: key) ifFalse: [url addParameter: key
value: value]]].
        ^self redirectResponseFor: url

WARegistry>>expiryPathFor: request on: url
        url
                addToPath: request url;
                addParameter: 'expired'

Cheers!

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: [hidden email] [mailto:seaside-
> [hidden email]] On Behalf Of Boris Popov
> Sent: Wednesday, October 10, 2007 4:15 PM
> To: Seaside - general discussion
> Subject: [Seaside] Custom WAApplications?
>
> What was the latest on removing #applicationClass and allowing custom
> subclasses of WAApplication? I personally couldn't care less for it,
but
> it seems to be the only clean way of overriding #expiryPathFor: and I
do

> recall having this conversation before, just can't recall the
> conclusion.
>
> Thanks!
>
> -Boris
>
> --
> +1.604.689.0322
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> http://tinyurl.com/r7uw4
>
> [hidden email]
>
> CONFIDENTIALITY NOTICE
>
> This email is intended only for the persons named in the message
> header. Unless otherwise indicated, it contains information that is
> private and confidential. If you have received it in error, please
> notify the sender and delete the entire message including any
> attachments.
>
> Thank you.
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Custom WAApplications?

Lukas Renggli
In reply to this post by Boris Popov, DeepCove Labs (SNN)
> What was the latest on removing #applicationClass and allowing custom
> subclasses of WAApplication? I personally couldn't care less for it, but
> it seems to be the only clean way of overriding #expiryPathFor: and I do
> recall having this conversation before, just can't recall the
> conclusion.

Well, there is this WARedirectHandler class that solved exactly this
problem. Unfortunately it got lost in the process of rewriting the
render-loop. Somebody would need to invest a little time to bring it
back ... let's see, it should happen soon sometime.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Custom WAApplications?

Lukas Renggli
> Well, there is this WARedirectHandler class that solved exactly this
> problem. Unfortunately it got lost in the process of rewriting the
> render-loop. Somebody would need to invest a little time to bring it
> back ... let's see, it should happen soon sometime.

http://bugs.squeak.org/view.php?id=6497

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside