It's funny you should ask. :-)

http://michael.merickel.org/2011/8/23/outgrowing-pyramid-handlers/
On Aug 24, 2011 6:24 AM, "Graham Higgins" <[email protected]> wrote:
>
>
>> Particular thanks to Michael Merickel for this release; much of the
>> code and design in 1.2 is his.
>>
>
> Hats off to MM for the solid contrib. I've been following progress on the
> #pyramid
> irc log (my TZ=GMT so I'm generally obliged to follow the discussions
using
> the irclog)
> ... and my attention was drawn to a remark that Michael recently made on
> #pyramid:
>
> Q: Are using Handlers kinda frowned upon? Coming from Pylons and
> sorta at a fork-in-the-road of whether I should just abandon my old habits

> or not
>
> raydeo: they are fine.. you don't gain a lot by using them though,
> especially if
> you don't care about dispatching to a view based on {action}
> patterns
> raydeo: and in 1.2 that will be solved more directly using just regular
> views
> raydeo: in general I would describe handlers as a crutch :-)
>
> okay, I note the smiley but I'd also be interested in a more detailed
> explanation of
> the programming / software engineering rationale that underpins a view of
> handlers
> as a crutch as this doesn't seem to be explored anywhere in the narrative
> docs.
>
> Cheers,
>
> Graham
>
> --
> You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
> To view this discussion on the web visit
https://groups.google.com/d/msg/pylons-discuss/-/hJvW4DMsP_AJ.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
[email protected].
> For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to