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 to the url to trigger the method(s) Iike:

http://mydomain.com/folder_to_resource/resource_id/get_resource
http://mydomain.com/folder_to_resource/resource_id/modify_resource
etc..

I am not using xhtml for my exchange but another xml format.

I was originally thinking of using a different port for this which is reason for possible use of webdav port instead of regular port.

Regards,
David

On Monday, November 28, 2005, at 09:26 AM, Tres Seaver wrote:

-----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 the current webdav server could be modified to handle requests
for this purpose.  I wondered how sensible this would be and whether
anyone else has considered this or other options for setting up another
listener for this type of service to their sites.

REST Web Service Conventions:

- Plain XML is the data representation format.

That isn't part of REST at all.  RESTified applications can be built
using *any* fileish representation.

- HTTP is the transfer protocol.
- HTTP's GET, POST, PUT, and DELETE are the access/manipulation verbs.

Zope already supports applicatoins built around the standard HTTP verbs.
 The trickiest thing about REST from Zope's point of view is that its
proponents seem to think POST (which is a general purpose verb) should
only be used for "resource creation".  Zope is happy to map POST / GET
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.

- URIs point to individual data records (such as catalog items or
customer info).

Already doable, and in fact done in many Zope applications.

- HTTP authentication and SSL provide security.

Likewise.  Basically, Zope already provides everything you need, and
more (not using the "more" is the hard part).


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

iD8DBQFDiwV/+gerLs4ltQ4RAjavAJ9PnKZ8rhVi9ZsyCIbrH02tNjzamgCgrsLL
iY2u2jHWvH5uT3riUtK+coQ=
=B+lA
-----END PGP SIGNATURE-----

_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )

_______________________________________________
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to