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
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
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
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
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
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
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
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
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
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
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
11 matches
Mail list logo
