Roger Ineichen wrote: >> The most convincing reason for me to persevere with the >> current pattern of views is that it offers the possibility of >> adaption on the request. >> This is something that repoze.bfg is exploring and I think >> could be helpful, for instance registering separate views on >> POSTRequest from GETRequest. >> >> I don't see anything wrong in allowing a utility access to >> the request without explicitly including it in its method >> signature. If they choose to use it from a model, it's their >> foot and they are free to shoot it if they wish. > > Why should someone use a global request if he has a request > available? This package does nothing else then offer a request > if non is available. And if you need a request if non is available > there is something wrong with the application design. Or better > let's say it's another pattern then we use in zope 3 right now.
Yes, it is a different pattern to the one used by pure zope 3 right now, but it is a pattern that would have allowed the transition of CMF tools to utilities. "The perfect is the enemy of the good." - Voltaire Laurence _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
