[Seaside-dev] about issue 103

[Julian Fitzell]

No strong opinions (don't like the #do... version of the method name)
but I'm wondering if you could explain what was the goal behind having
the request handlers push themselves onto a stack. I'm not questioning
it (seems like it could be useful), I'm just curious what you are
planning to use the information for, having missed out on that
discussion, obviously.

Julian

On Sat, Aug 2, 2008 at 1:02 AM, Philippe Marschall
<philippe.marschall at gmail.com> wrote:
> Hi
>
> I think it's time we fix:
> http://code.google.com/p/seaside/issues/detail?id=103
>
> I think we should provide a method that is like #handleRequest: with
> the difference that the receiver is already in the request context.
> Originally I thought about a subclass like WAPushingRequestHandler but
> I now favor doing it in WARequest handler. It would be something like
> this.
>
> handleRequest: aRequest
>   "some helpful comment"
>    ^self pushSelfDuring: [ self yetDoBeDecidedSelector: aRequest  ]
>
> - #handleRequestPushed:
> - #doHandleRequest:
>
> Any comments, issues, suggestions, dislikes, ....?
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>