Roger Ineichen wrote: > I see your point. I'm not saying that this is bad in general. > Probably "when used in moderation" is the right concept for this > package ;-)
and it wasn't written with anything else in mind -- merely for the odd case when you need a request object, but none has been passed around. imho, it makes more sense to use a defined API in those cases instead of relying on knowledge about the current implementation. i mean, sometimes it's not possible to adjust the design and change all of the involved code (at least not timely), in which case people may resolve to simply fetch the request from anywhere they know it's accessible. a common API does help here, especially when it comes to changing things. but like i said, that's not supposed to mean `zope.globalrequest` was to promote a new pattern for zope development. cheers, andi -- zeidler it consulting - http://zitc.de/ - i...@zitc.de friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.1.5.1 released! -- http://plone.org/products/plone/ _______________________________________________ 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 )
