Brad Clements wrote:
PythonScript.py line 368 or so
def PUT(self, REQUEST, RESPONSE):
Handle HTTP PUT requests
self.dav__init(REQUEST, RESPONSE)
self.dav__simpleifhandler(REQUEST, RESPONSE, refresh=1)
self.write(REQUEST.get('BODY', ''))
On 29 Nov 2005 at 9:53, Chris Withers wrote:
Brad Clements wrote:
PythonScript.py line 368 or so
def PUT(self, REQUEST, RESPONSE):
...well, you could always subclass and override ;-)
Plus that method is protected by Change Python Scripts permission
as well.
Why is that
(Sun, Nov 27, 2005 at 12:00:08PM -0500) [EMAIL PROTECTED] wrote/schrieb/egrapse:
Am Samstag, den 26.11.2005, 21:17 -0400 schrieb David Pratt:
Hi. I am looking at how to implement a RESTful web service in Zope2.
Could you expand a bit on whatever a RESTful web service is?
Hi Tino,
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Pratt wrote:
Hi Tino.
Here are a couple of links that describe it. Boils down to using
regular GET, POST, PUT, and DELETE over HTTP using specific URI's to
invoke actions - sort of like XMLRPC over HTTP. It occurred to me that
perhaps
Hi. Thanks Tres and Sascha for replies. Sascha, I think this is right
way to go and will make a product to do this and put the templates into
skins. As far as URL's, I was hoping to do something like:
http://mydomain.com/folder_to_resource/resource_id
but I guess it will be enough to append
Yeah, if POST and GET are desired to have semantic differences, your
code will have to explicitly check request['REQUEST_METHOD'].
On 11/28/05, Tres Seaver [EMAIL PROTECTED] wrote:
The trickiest thing about REST from Zope's point of view is that its
proponents seem to think POST (which is a
On 28 Nov 2005 at 8:26, Tres Seaver wrote:
requests onto *any* publishable method, which means that you have to
try hard to abide by the RESTriction. Zope also supports using PUT
for resource creation, which the REST folks don't seem to get.
I'm not sure what part REST folks don't seem to
