Re: [Zope3-dev] Re: Deploying WSGI Apps with Zope 3.2+
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: On Thu, Jan 26, 2006 at 02:02:19PM +, Chris Withers wrote: | Sidnei da Silva wrote: | > | >My original intention was to put the config file location in the | >ZConfig schema, but that's *wy* too painful right now. | | What's the specific problem here? I find adding to ZConfig schemas | pretty easy... Yet you find ZCML declaring namespaces in ZCML files annoying *wink*. Sometimes I don't understand you :) +1 to that. I think Chris doesn't really believe in the Second Law of Python (according to the prophet Peters). No, Chris just doesn't like XML namespaces. You can still have explicitness without XML namespaces. I think I'm starting to grasp the XML division among Zope developers. ZConfig schema definitions use a conventional style of XML with deeply nested elements, text nodes, and no namespaces, while ZCML uses its own style with minimal nesting, many attributes, and many namespaces. Many of us have a strong preference for one style or the other and we're perplexed that others would actually prefer their crazy style. I remember that Jim once presented two XML samples and asked which one was more readable. I preferred many elements over many attributes. He preferred the opposite. I thought he was crazy, and as I recall, he thought I was crazy, too. :-) This division probably exists because there is no widely accepted "Zen of XML". Perl and C/C++ programmers have a similar problem. From what I can tell, open source Perl and C/C++ projects solve the problem by either combining many styles, or by telling contributors they have to mimic the style the existing code uses, regardless of how peculiar the style is. Eh... I guess every mailing list ends up battling over style concerns. The least important issues lead to the biggest battles. After I throw some quotes and colons at you, you can throw some angle brackets and ambiguous whitespace at me, then we'll call a truce. :-) Shane ___ 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+
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: > On Thu, Jan 26, 2006 at 02:02:19PM +, Chris Withers wrote: > | Sidnei da Silva wrote: > | > > | >My original intention was to put the config file location in the > | >ZConfig schema, but that's *wy* too painful right now. > | > | What's the specific problem here? I find adding to ZConfig schemas > | pretty easy... > > Yet you find ZCML declaring namespaces in ZCML files > annoying *wink*. Sometimes I don't understand you :) +1 to that. I think Chris doesn't really believe in the Second Law of Python (according to the prophet Peters). > Tres' ZConfig products extension thing just enables you to use > key-value pairs, without being able to specify what the datatypes for > those values are, if I'm not mistaken. That was the first thing Fred and I checked in. http://svn.zope.org/Zope/?view=rev&rev=39635 We then added (later that morning) the ability to declare new abstract section types: http://svn.zope.org/Zope/?view=rev&rev=39652 > Also, AFAICT it's not present in Zope 3 yet. The changes were to Zope2-specific schema stuff; I'm not even sure where they would fit into Zope3. > What I think is that the Zope ZConfig schema should have something > just like 'package-includes' is for ZCML. A place where you can drop a > snippet of ZConfig schema and it will get picked up at boot time. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD2X5n+gerLs4ltQ4RAl/GAJ90Nv7VnBVFnL4G4RF+6lWiEtoQ5wCggnAc 53PlWd1z7wOaGB51dAM6yjE= =YFbN -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Class Diagrams
Tim Peters wrote: [David Johnson] Does anyone have any class diagrams of Zope 3? Specifically related to ZODB? There's a UML model for ZODB here: http://www.zope.org/Documentation/Developer/Models/ZODB linked to from ZODB's home page: http://www.zope.org/Wikis/ZODB/FrontPage The model is partly out of date, and navigating through the 4-pane interface can be frustrating, but there's a lot of good info there. Alas, I'm not sure anyone still has the software that created this to begin with, so it never gets (& most likely never will be) updated. We have the software, but the model file is corrupt and can't be read anymore. 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] Class Diagrams
[David Johnson] > Does anyone have any class diagrams of Zope 3? Specifically related to > ZODB? There's a UML model for ZODB here: http://www.zope.org/Documentation/Developer/Models/ZODB linked to from ZODB's home page: http://www.zope.org/Wikis/ZODB/FrontPage The model is partly out of date, and navigating through the 4-pane interface can be frustrating, but there's a lot of good info there. Alas, I'm not sure anyone still has the software that created this to begin with, so it never gets (& most likely never will be) updated. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Class Diagrams
Does anyone have any class diagrams of Zope 3? Specifically related to ZODB? -- David Johnson [EMAIL PROTECTED] 201 Main Street Suite 1320 Fort Worth, TX 76102 (877) 572-8324 x2200 ___ 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
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] 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. > >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
[Zope3-dev] xmlrpc:view (and jsonrpc:view)
I have been watching with some interest the thread about zcml simplification (ZCML bad et.al.), and of course I looked at Philipp's list of things that could be dead chickens in ZCML. I agree with most, and even with the directive. My question starts with the fact that for the jsonserver package, I copied the pattern for JSON-RPC. Should xmlrpc views be browser:views, and more specifically for me, should jsonrpc views be browser:views? Do we really need other types of views than browser:views? It seems that the different uses are entirely up to the developer, and not specifically controlled by Zope3, anyway. I have discovered, for example, that a browser:view can be accessed through jsonrpc just fine; it just gets wrapped in JSON-RPC syntax, which is actually pretty nice if you want to have multi-use of a page snippet for page composition then later for AJAXish insertion by the client. Anyway, I am considering removing the jsonrpc:view directive from my third-party project (to be replaced by the already available browser:view), and am wondering if there is a risk I have not considered. The main risk I see is angry customers, but I think I can calm them by explaining the added simplicity it brings. -Jim Washington it-seemed-to-be-the-right-thing-to-do-at-the-moment ___ 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 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. ditto from me. Extending ZConfig is tough, but ZCML meta directives and schemas are so easy to use. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ 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+
Chris Withers wrote: Sidnei da Silva wrote: My original intention was to put the config file location in the ZConfig schema, but that's *wy* too painful right now. What's the specific problem here? I find adding to ZConfig schemas pretty easy... 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. 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
[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: [...] | 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. [...] | Does anybody care about using eggs with Zope 3.2? This is not an immediate concern of mine. If it is important enough to you, you could make a 'Zope-3.2-plus-eggs' branch of the Zope-3.2 branch. In that branch you can add whatever is necessary for eggs and when (if) the time for a 3.2.1 release comes people can reevaluate if that should be in that release. -D -- mailhost:/etc/mail# less sendmail.cf less: syntax of file "sendmail.cf" may induce nausea, show anyway? [n] www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature ___ 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 02:02:19PM +, Chris Withers wrote: | Sidnei da Silva wrote: | > | >My original intention was to put the config file location in the | >ZConfig schema, but that's *wy* too painful right now. | | What's the specific problem here? I find adding to ZConfig schemas | pretty easy... Yet you find ZCML declaring namespaces in ZCML files annoying *wink*. Sometimes I don't understand you :) Tres' ZConfig products extension thing just enables you to use key-value pairs, without being able to specify what the datatypes for those values are, if I'm not mistaken. Also, AFAICT it's not present in Zope 3 yet. What I think is that the Zope ZConfig schema should have something just like 'package-includes' is for ZCML. A place where you can drop a snippet of ZConfig schema and it will get picked up at boot time. -- 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 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+
Sidnei da Silva wrote: My original intention was to put the config file location in the ZConfig schema, but that's *wy* too painful right now. What's the specific problem here? I find adding to ZConfig schemas pretty easy... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Zope definition on Wikipedia
I have made a little update on the Zope article on Wikipedia: http://en.wikipedia.org/wiki/Zope Here is the diff: http://en.wikipedia.org/w/index.php?title=Zope&diff=36787848&oldid=36094466 It would probably be very helpful if some knowledgeable people would also take some time to review the whole content of the article. Maybe split Zope 3 to a separate page, or at least start a page on the component architecture. A paragraph about Five would also be helpful. There are also some disputable assertions, like this one "More recently the Zope community branched in two directions. The Plone community turned Zope into a nice-looking content management system, complete with modern well-designed style sheets. The original authors released Zope 3." that should be corrected. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ 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
[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 is. | >| | >| Why is this necessary? | > | >So the config file for paste.deploy can be in /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 '/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=41449&view=markup Thoughts? -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +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] 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 is. | >| | >| Why is this necessary? | > | >So the config file for paste.deploy can be in /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. Sure. > 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 '/etc/paste.ini' than configurable at this point. Sure, for a prototype. In the long term, explicit is better than implicit. > 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 don't agree. Paste Deploy encourages use of multiple configution files: - to reuse configuration - to override configuration 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. Maybe, but I don't want to simply pile hack on cruft on hack. 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] 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
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 is. | >| | >| Why is this necessary? | > | >So the config file for paste.deploy can be in /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 '/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=41449&view=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] 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 is. | | Why is this necessary? So the config file for paste.deploy can be in /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] 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
