Re: [Zope3-dev] Re: Question about re-authentication
On Wed, 2006-01-25 at 17:25 -0500, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Wednesday 25 January 2006 05:40, Christian Theune wrote: I'm quite sure that part b) isn't written yet, but I'm not sure what the state of part a) is. (a) is done. It is indeed the default Zope behavior. Hmm, I thought that Zope3's security machinery set the response code to 403 (forbidden) rather than a 401 (Unauthorized) if the user is already authenticated. but then tries to do something not allowed. Browsers (rightfully) don't treat a 403 as a prompt to reauthenticate. The configureed authentication service *may* override that to raise Unauthorized, but that is not mandated. I think Zope has a notion of saying there is no way you could authorize to do this and well. you can't do this now, but you might be able. I think the first thing would be totally private stuff (like in Zope 2 using declarePrivate()) whereas the second thing would be things where the user just misses a permission. AFAIK things without permission declarations are private and the user stands no chance to provide credentials that give him enough grants. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Deploying WSGI Apps with Zope 3.2+
Sidnei da Silva wrote: On Wed, Jan 25, 2006 at 05:28:14PM -0500, Jim Fulton wrote: | There are a bunch of issues to be resolved, like the fact that it's | not possible to access the initial ZConfig options object because it's | thrown away, so, in order of priority: | | 1. It's not possible to find where the INSTANCE_HOME is. | | Why is this necessary? So the config file for paste.deploy can be in INSTANCE_HOME/etc/paste.ini Hm. I don't have the time to think hard about this right now, but I suspect the model you are following isn't quite right. Rather than implicitly looking for a paste file in a magic location, I suspect that you should name the paste file in your ZConfig file or possibly extend the ZConfig schema with components that reproduce what's normally found in a paste config file (app definitions, server definitions, etc.). Of course, either of these options requires updating the ZConfig schema which is a real pain, so I can understand why you wouldn't want to do that. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Deploying WSGI Apps with Zope 3.2+
On Thu, Jan 26, 2006 at 06:30:02AM -0500, Jim Fulton wrote: | Sidnei da Silva wrote: | On Wed, Jan 25, 2006 at 05:28:14PM -0500, Jim Fulton wrote: | | There are a bunch of issues to be resolved, like the fact that it's | | not possible to access the initial ZConfig options object because it's | | thrown away, so, in order of priority: | | | | 1. It's not possible to find where the INSTANCE_HOME is. | | | | Why is this necessary? | | So the config file for paste.deploy can be in INSTANCE_HOME/etc/paste.ini | | Hm. I don't have the time to think hard about this right now, | but I suspect the model you are following isn't quite right. Rather than | implicitly looking for a paste file in a magic location, I suspect that you | should name the paste file in your ZConfig file or possibly extend the | ZConfig | schema with components that reproduce what's normally found in a paste | config | file (app definitions, server definitions, etc.). Of course, either of | these | options requires updating the ZConfig schema which is a real pain, so I can | understand why you wouldn't want to do that. And you're right to the point. My original intention was to put the config file location in the ZConfig schema, but that's *wy* too painful right now. OTOH, it does seem to work pretty reasonably right now to serve as a prototype. I have other concerns than if the config file location is magic or not at the moment. I mean, it's probably better that it's hardcoded to 'INSTANCE/etc/paste.ini' than configurable at this point. I don't think one would need *more than one* paste.deploy configuration file anyway, so changing it's name would be pretty pointless. I think we can slowly progress from here, solving the ZConfig problem, then the server-type-always-takes-db-argument and eventually end up with zope.paste in the main tree and having the default wsgi server be configured using paste.deploy. BTW, I've updated the README.txt to include a more extensive description of how to use it right now: http://svn.zope.org/zope.paste/trunk/README.txt?rev=41449view=markup Thoughts? -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/branches/3.2/ - Declare the zope top-level package as a namespace package if
On Wed, Jan 25, 2006 at 04:37:45PM -0200, Sidnei da Silva wrote: | On Wed, Jan 25, 2006 at 01:30:41PM -0500, Stephan Richter wrote: | | Please revert this revision. As you admit yourself in CHANGES.txt, this is a | | new feature. You cannot add new features to a dot release branch. | | Well, I would go as far as calling it a bugfix. Will revert it then we | can discuss. Sorry, I've removed some context from this email, so I guess nobody understood what it is about. I had added a call to pkg_resource.declare_namespace() to Zope 3's zope/__init__.py, which enables one to have sub packages of 'zope' distributed as eggs. Stephan complained that this is not a 'bugfix' but a 'new feature' and asked me to revert, which I promptly did. I suspect that no new Zope 3.2.x release will come out soon anyway, so maybe it doesn't make sense to add it there really, but it would be really nice to have this feature available before the 3.3 release. Does anybody care about using eggs with Zope 3.2? -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Deploying WSGI Apps with Zope 3.2+
Sidnei da Silva wrote: On Thu, Jan 26, 2006 at 06:30:02AM -0500, Jim Fulton wrote: | Sidnei da Silva wrote: | On Wed, Jan 25, 2006 at 05:28:14PM -0500, Jim Fulton wrote: | | There are a bunch of issues to be resolved, like the fact that it's | | not possible to access the initial ZConfig options object because it's | | thrown away, so, in order of priority: | | | | 1. It's not possible to find where the INSTANCE_HOME is. | | | | Why is this necessary? | | So the config file for paste.deploy can be in INSTANCE_HOME/etc/paste.ini | | Hm. I don't have the time to think hard about this right now, | but I suspect the model you are following isn't quite right. Rather than | implicitly looking for a paste file in a magic location, I suspect that you | should name the paste file in your ZConfig file or possibly extend the | ZConfig | schema with components that reproduce what's normally found in a paste | config | file (app definitions, server definitions, etc.). Of course, either of | these | options requires updating the ZConfig schema which is a real pain, so I can | understand why you wouldn't want to do that. And you're right to the point. My original intention was to put the config file location in the ZConfig schema, but that's *wy* too painful right now. I thought Tres had added to ZConfig the possibility to have arbitrary key/values for arbitrary additional products. Or was this only in the context of Zope 2 ? Florent OTOH, it does seem to work pretty reasonably right now to serve as a prototype. I have other concerns than if the config file location is magic or not at the moment. I mean, it's probably better that it's hardcoded to 'INSTANCE/etc/paste.ini' than configurable at this point. I don't think one would need *more than one* paste.deploy configuration file anyway, so changing it's name would be pretty pointless. I think we can slowly progress from here, solving the ZConfig problem, then the server-type-always-takes-db-argument and eventually end up with zope.paste in the main tree and having the default wsgi server be configured using paste.deploy. BTW, I've updated the README.txt to include a more extensive description of how to use it right now: http://svn.zope.org/zope.paste/trunk/README.txt?rev=41449view=markup Thoughts? -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/branches/3.2/ - Declare the zope top-level package as a namespace package if
Sidnei da Silva wrote: Does anybody care about using eggs with Zope 3.2? It seems like a stretch to call making 3.2 work with eggs a bug fix. But it's probably a moot point if we change the release cycle to be May/November, 3.3 would be out pretty quickly. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/branches/3.2/ - Declare the zope top-level package as a namespace package if
On Thu, Jan 26, 2006 at 09:50:29AM -0200, Sidnei da Silva wrote: On Wed, Jan 25, 2006 at 04:37:45PM -0200, Sidnei da Silva wrote: | On Wed, Jan 25, 2006 at 01:30:41PM -0500, Stephan Richter wrote: | | Please revert this revision. As you admit yourself in CHANGES.txt, this is a | | new feature. You cannot add new features to a dot release branch. | | Well, I would go as far as calling it a bugfix. Will revert it then we | can discuss. Sorry, I've removed some context from this email, so I guess nobody understood what it is about. I had added a call to pkg_resource.declare_namespace() to Zope 3's zope/__init__.py, which enables one to have sub packages of 'zope' distributed as eggs. Stephan complained that this is not a 'bugfix' but a 'new feature' and asked me to revert, which I promptly did. I suspect that no new Zope 3.2.x release will come out soon anyway, so maybe it doesn't make sense to add it there really, but it would be really nice to have this feature available before the 3.3 release. Does anybody care about using eggs with Zope 3.2? I care about not adding this functionality in a stable release as I am totally unsure of how it will affect the Debian packaging of Zope. Debian packaging and eggs do not see eye to eye sometimes. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/jinty%40web.de -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Deploying WSGI Apps with Zope 3.2+
Stephan Richter wrote at 2006-1-26 10:16 -0500: On Thursday 26 January 2006 10:04, Jim Fulton wrote: Every change I've ever been involved with has been extremely painful. I can't even explain well what made it painful because I didn't really understand what was going on and needed help from Fred. Maybe someone would make the same comment about ZCML, although I've had a lot of positive feedback on the ZCML extension mechanisms. shrug/ Extending ZConfig is tough Chris and me find it easy... but ZCML meta directives and schemas are so easy to use. I do not yet know ZCML... When I have read your book I was scared away from ZCML by the amount of namespaces and directives -- in addition that I do not like the XML hype (that part that seems to imply that as soon as something is XML it is also easy and well understood). -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Missing environment and configuration
Jim Fulton wrote at 2006-1-25 17:26 -0500: Sidnei da Silva wrote: In Zope 2, we had excess of configuration options and environment variables. How did you have access to configuration options? from App.config import getConfiguration; config = getConfiguration(). -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Deploying WSGI Apps with Zope 3.2+
Florent Guillaume wrote at 2006-1-26 12:57 +0100: ... I thought Tres had added to ZConfig the possibility to have arbitrary key/values for arbitrary additional products. Or was this only in the context of Zope 2 ? It is essentially the %import package extension of ZConfig. It allows package to define its own sections types. Almost surely, %import is already available in the ZConfig version for Zope 3. The additional piece necessary is a placeholder in the schema itself consisting of a multisection of some abstract type. To define package specific extensions, the package can implement this abstract type. This part might not yet be in the Zope 3 schema. -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
