[Seaside-dev] moving document handlers to session

Julian Fitzell jfitzell at gmail.com
Sun Jan 22 15:07:13 UTC 2012


Thinking totally off the top of my head, but what if it was implemented as
a filter? A few helper methods on WARequestHandler (or subclasses) could
add an instance if it's missing and then add the document and return a
URL...

Julian

On Sun, Jan 22, 2012 at 1:57 PM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:

> Hi
>
> I hope an can attend the Pharo Sprint at Feb 18./19. and repurpose it
> to hack on Seaside. One thing I'd like to do is moving the document
> handlers from registry to session.
>
> Pros:
>  * simple
>  * adding a document handler no longer potentially expires a session
>  * expiring a session expires all it's document handlers
>  * session tracking code becomes much simpler
>
> Cons:
>  * #urlXXX methods on WARenderContext only work with sessions (a
> fallback could be added in theory)
>  * #urlXXX methods on WARenderContext need to become class extensions
> of the Seaside-Session package
>  * not really clean framework-framework Endlösung
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20120122/0f076c3c/attachment.htm


More information about the seaside-dev mailing list