[Zope-dev] zope.globalrequest?

Roger Ineichen dev at projekt01.ch
Sun Jan 18 08:59:34 EST 2009


Hi Andi

> Betreff: Re: [Zope-dev] zope.globalrequest?
> 
> Roger Ineichen wrote:
> > I don't say that this is bad in general. I just say that if 
> you build 
> > an application based on zope.globalrequest, this is a 
> totaly different 
> > base concept how you will develop applications like we do 
> now. And you 
> > have to pay the price with a complex test setup.
> 
> it's merely one more package and its zcml (setting up two 
> event subscribers).  considering the complexity of the stack 
> as we know it i don't think it really adds that much, no?

I think it's more then that

It changes the way you will think about MVC and the way you develop
and take care on separate your model, view controller components.

It's like aquisition in Zope 2, you don't have to take care where
your attributes coming from, they're just there. Doesn't matter
if this is good or bad, it's just a very different concept.

Defently a bad thing is, if to many developer start using
zope.globalrequest in their 3rd party packages. We can't reuse
this 3rd party packages whithout using a global request variable.

In my point of view it's a fundamental change on what an application
is built on. Probably the good thing is, it's easy to provide such
a global request as long as you use a webserver (publisher).

just a sample;
In my point of view an application like a wiki or forum etc.
should get developed as a python application without to require
a global request because it's just a (MVC) model part. There should
never be a request involved. If such a wiki needs a "last modified user"
argument. This should not get set by a global request lookup.
Or at least not the model should use such a global request by itself.
If you need to set such a "last user modified" argument the view/controller
should be responsible for doing so. I'm pretty sure if we have a global
request available we will see very quick that developer start to use
the global request in the model part.

Note, mixin model, view and controller responisibilities into one 
component/object make it allmost impossible to replace or reuse
parts of it.

Regards
Roger Ineichen

> best regards,
> 
> 
> andi
> 
> --
> zeidler it consulting - http://zitc.de/ - info at 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.7 released! -- http://plone.org/products/plone/
> 
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev at 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 )
> 



More information about the Zope-Dev mailing list