Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
On Thursday 20 December 2007, Ignas Mikalajunas wrote: In SchoolTool we used to start another server for REST to have a different Publication for REST calls. I like that approach best too. I decided to use it in z3c.rest. A custom publication object allows you to implement an API that makes most sense for a RESTive API. I am still playing around to see what the best API is though. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Am Freitag, den 21.12.2007, 12:39 -0500 schrieb Jim Fulton: Good job! :) I agree that this is really annoying. Really, this needs to get unscrewed. I'm skeptical that this is released in 3.4 since a dependency on an unreleased alpha egg is involved. It turns out that there are separate issues around. This breakage does not relate to the XML-RPC `skin` traversal, see my other post. Christian -- gocept gmbh co. kg - forsterstrasse 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: Dies ist ein digital signierter Nachrichtenteil ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hi, Am Freitag, den 21.12.2007, 10:28 +0100 schrieb Christian Theune: We have different to topics that need discussion/decision: a) There is breakage in publisher eggs for which the XML-RPC stuff assumed to be the reason. I'll figure out what's going on there today so that the immediate breakage goes away. Update: I looked at this and the issue is not the XML-RPC stuff, but installing an egg with the correct extra to let the tests get all required dependencies for testing. b) We intended to remove the functionality this week as it was not agreed on to include. However, we (gocept) found that it was already released in the 3.4 series as we (gocept) let the topic slip for too long. This means we can't just take it out again. We (gocept) 're honestly sorry this happened. How shall we proceed? I was wrong, the XML-RPC features went into the trunk (3.5) only. I'll move those changes to a branch that we (gocept) can continue to use for now and clean up the trunk from our changes. Christian -- gocept gmbh co. kg - forsterstrasse 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: Dies ist ein digital signierter Nachrichtenteil ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hi, Am Freitag, den 21.12.2007, 10:28 +0100 schrieb Christian Theune: b) We intended to remove the functionality this week as it was not agreed on to include. However, we (gocept) found that it was already released in the 3.4 series as we (gocept) let the topic slip for too long. This means we can't just take it out again. We (gocept) 're honestly sorry this happened. How shall we proceed? I have removed the XML-RPC layer support by backing out the related changes from zope.publisher, zope.app.publisher and zope.traversing. zope.app.publisher and zope.traversing had alpha releases. I superseded those by making another alpha release. The up-to-date packages in PyPI now neither provide nor require a package with the XML-RPC skin support. zope.publisher did not have a released version including the XML-RPC skin support yet, so I ommitted making a release here. I created branches `3.5-gocept-xmlrpc-skin` of the affected packages so our existing projects can keep using those in the short term until we find another solution. Christian -- gocept gmbh co. kg - forsterstrasse 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: Dies ist ein digital signierter Nachrichtenteil ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hey, Am Freitag, den 21.12.2007, 09:58 +0100 schrieb Christian Zagrodnick: Yes, what do others think? It's quite hard for me to do anything because the discussion is kind of nebulous. We have different to topics that need discussion/decision: a) There is breakage in publisher eggs for which the XML-RPC stuff assumed to be the reason. I'll figure out what's going on there today so that the immediate breakage goes away. b) We intended to remove the functionality this week as it was not agreed on to include. However, we (gocept) found that it was already released in the 3.4 series as we (gocept) let the topic slip for too long. This means we can't just take it out again. We (gocept) 're honestly sorry this happened. How shall we proceed? c) There is a need for a general solution regarding the issue of providing a `request typing` mechanism for various protocols (including sub-protocols of HTTP). Skins are one implementation, the XML-RPC skinning is another implementation. For this we should start writing a proposal that can be discussed. It's getting hard to follow what the goals, steps, risks and their assessments/counter measures are. Writing a proposal and adjusting it over time would be best here. Christian -- gocept gmbh co. kg - forsterstrasse 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: Dies ist ein digital signierter Nachrichtenteil ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Good job! :) I agree that this is really annoying. Really, this needs to get unscrewed. I'm skeptical that this is released in 3.4 since a dependency on an unreleased alpha egg is involved. Jim On Dec 21, 2007, at 12:32 PM, Chris McDonough wrote: I also have zero opinion about this but I'll note as the dedicated whiner, that, delta some policy change, until this gets worked out, the Cheese Shop is broken for people who want to install zope.app* packages (and other related packages). A release of zope.traversing has a dependency on another release that doesn't exist in the index. Somebody made the decision to keep it as-is until this issue gets worked out. It has been broken now for roughly two and a half weeks. - C On Dec 20, 2007, at 5:13 AM, Martijn Faassen wrote: Hey, Christian Zagrodnick wrote: a couple of weeks ago there was some discussion about the skin/ layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it. Let me first summarise: * Skin and layers should be seen as typing the request. * There are no general objections against having layers for XML-RPC. * There are objections against using ++skin++ for XML-RPC, ++api++ would be fine. I don't really have time to read this whole discussion, but note that Grok's REST support uses ++rest++protocolname and then provides a rest layer (for that protocol) to the request. That sounds quite similar to what you are proposing for XMLRPC. It's still ugly as POST and GET need to be handled by something else than PUT and DELETE, unfortunately; you can't use a different publisher (publication? whatever the name is for this handle) for GET and POST as the interface isn't set at the point it kicks in. Regards, Martijn ___ 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 ) ___ 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 ) -- Jim Fulton Zope Corporation ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
I also have zero opinion about this but I'll note as the dedicated whiner, that, delta some policy change, until this gets worked out, the Cheese Shop is broken for people who want to install zope.app* packages (and other related packages). A release of zope.traversing has a dependency on another release that doesn't exist in the index. Somebody made the decision to keep it as-is until this issue gets worked out. It has been broken now for roughly two and a half weeks. - C On Dec 20, 2007, at 5:13 AM, Martijn Faassen wrote: Hey, Christian Zagrodnick wrote: a couple of weeks ago there was some discussion about the skin/ layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it. Let me first summarise: * Skin and layers should be seen as typing the request. * There are no general objections against having layers for XML-RPC. * There are objections against using ++skin++ for XML-RPC, ++api++ would be fine. I don't really have time to read this whole discussion, but note that Grok's REST support uses ++rest++protocolname and then provides a rest layer (for that protocol) to the request. That sounds quite similar to what you are proposing for XMLRPC. It's still ugly as POST and GET need to be handled by something else than PUT and DELETE, unfortunately; you can't use a different publisher (publication? whatever the name is for this handle) for GET and POST as the interface isn't set at the point it kicks in. Regards, Martijn ___ 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 ) ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hey, Am Freitag, den 21.12.2007, 12:32 -0500 schrieb Chris McDonough: I also have zero opinion about this but I'll note as the dedicated whiner, that, delta some policy change, until this gets worked out, the Cheese Shop is broken for people who want to install zope.app* packages (and other related packages). A release of zope.traversing has a dependency on another release that doesn't exist in the index. Somebody made the decision to keep it as-is until this issue gets worked out. It has been broken now for roughly two and a half weeks. Thanks for saying the name of the broken package. See my other post. I'll work on it tomorrow, depending on the surrounding conditions that might hinder me to actually resolve it. Christian -- gocept gmbh co. kg - forsterstrasse 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: Dies ist ein digital signierter Nachrichtenteil ___ 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 )
[Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hey, Christian Zagrodnick wrote: a couple of weeks ago there was some discussion about the skin/layer support for XML-RPC which I implemented without asking (shame on me). As some time has passed now everybody could have some fresh thoughts about it. Let me first summarise: * Skin and layers should be seen as typing the request. * There are no general objections against having layers for XML-RPC. * There are objections against using ++skin++ for XML-RPC, ++api++ would be fine. I don't really have time to read this whole discussion, but note that Grok's REST support uses ++rest++protocolname and then provides a rest layer (for that protocol) to the request. That sounds quite similar to what you are proposing for XMLRPC. It's still ugly as POST and GET need to be handled by something else than PUT and DELETE, unfortunately; you can't use a different publisher (publication? whatever the name is for this handle) for GET and POST as the interface isn't set at the point it kicks in. Regards, Martijn ___ 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 )
Re: [Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
I don't really have time to read this whole discussion, but note that Grok's REST support uses ++rest++protocolname and then provides a rest layer (for that protocol) to the request. That sounds quite similar to what you are proposing for XMLRPC. It's still ugly as POST and GET need to be handled by something else than PUT and DELETE, unfortunately; you can't use a different publisher (publication? whatever the name is for this handle) for GET and POST as the interface isn't set at the point it kicks in. Regards, Martijn In SchoolTool we used to start another server for REST to have a different Publication for REST calls. As now I have started using Paste to start up schooltool, and paste does not support 2 Zope3 servers running on different ports using the same WSGI application (at least i don't know how to do that in paste.ini) I have opted for a brute force solution - URL based dispatch in the SchoolToolWSGIApplication code that switches between publications and request types before Zope3 has a chance to pick the wrong set. So instead of 2 servers for both applications now i have 1 WSGI server, and a weird kind of midleware that selects the right application (while both applications share the component registry and ZODB). I kind of like it that way, I could even give the freedom for the user to select the REST url prefix that he likes/wants to have, just like he could configure the port of the REST server. Ignas ___ 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 )
[Zope-dev] Re: Request typing (to get the xmlrpc layer discussion finished)
Hey, Ignas Mikalajunas wrote: [REST in Grok] In SchoolTool we used to start another server for REST to have a different Publication for REST calls. As now I have started using Paste to start up schooltool, and paste does not support 2 Zope3 servers running on different ports using the same WSGI application (at least i don't know how to do that in paste.ini) I have opted for a brute force solution - URL based dispatch in the SchoolToolWSGIApplication code that switches between publications and request types before Zope3 has a chance to pick the wrong set. So instead of 2 servers for both applications now i have 1 WSGI server, and a weird kind of midleware that selects the right application (while both applications share the component registry and ZODB). I kind of like it that way, I could even give the freedom for the user to select the REST url prefix that he likes/wants to have, just like he could configure the port of the REST server. In Grok there's no WSGI setup necessary to do REST. I like it that way at present. Perhaps the WSGI route will start to make more sense once that matures significantly. Grok will do its bit to help mature the WSGI way, but until then I'm not convinced your approach is the easiest way? It sounds like quite a bit of additional setup is required compared to just writing REST views. Regards, Martijn ___ 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 )
