[XML-SIG] [Fwd: [Zope] - XML-RPC]

Jim Fulton jim.fulton@digicool.com
Fri, 22 Jan 1999 10:16:47 -0500

This is a multi-part message in MIME format.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I meant to CC the XML SIG mailing list in this message, but forgot

Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Received: from albert.digicool.com ([]) by gandalf.digicool.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3)
	id D1YQ5JFN; Fri, 22 Jan 1999 09:27:13 -0500
Received: from albert.digicool.com (localhost [])
	by albert.digicool.com (8.9.1/8.9.1) with ESMTP id JAA14284;
	Fri, 22 Jan 1999 09:19:43 -0500
Received: from digicool.com (glebe.digicool.com [])
	by albert.digicool.com (8.9.1/8.9.1) with ESMTP id JAA14261;
	Fri, 22 Jan 1999 09:19:24 -0500
Message-ID: <36A88774.DDF32151@digicool.com>
Date: Fri, 22 Jan 1999 09:13:08 -0500
From: Jim Fulton <jim.fulton@digicool.com>
Organization: Digital Creations, Inc.
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Skip Montanaro <skip@calendar.com>
CC: Pavlos Christoforou <pavlos@gaaros.msrc.sunysb.edu>, zope@zope.org
Subject: Re: [Zope] - XML-RPC
References: <Pine.LNX.3.96.990121140044.2354B-100000@gaaros.msrc.sunysb.edu> <13991.34599.787787.461627@dolphin.calendar.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: zope-admin@zope.org
List-Id: Zope -- The Z Object Publishing Environment <zope.zope.org>
Errors-To: zope-admin@zope.org
X-BeenThere: zope@zope.org
X-Mailman-Version: 1.0b6

I think that XML-RPC would almost certainly be a cool thing to 
support in Zope, and Zope would be a cool server for XML RPC. 
IMO, the right way to do it would be to add support for it to 

XML-RPC (http://www.scripting.com/frontier5/xml/code/rpc.html)
uses POST requests with content type "text/xml".  
(Does anyone but me think that this content type is a bit
too broad?) It would be straightforward for ZPublisher to 
recognize this case and:

 - Add the method supplied in the body to 
   the request path, 

 - Get method parameters (positionally)
   from the body.
I'm in favor of this but doubt that anyone here at DC
will have time to do this for some time.  I'd gladly
accept patches though, and would be willing to discuss
details with anyone working on such patches. ;)
In fact,  if anyone does work on this, I'd prefer to 
discuss it with them before they get too far.


Jim Fulton           mailto:jim@digicool.com
Technical Director   (888) 344-4332              Python Powered!
Digital Creations    http://www.digicool.com     http://www.python.org

Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email
address may not be added to any commercial mail list with out my
permission.  Violation of my privacy with advertising or SPAM will
result in a suit for a MINIMUM of $500 damages/incident, $1500 for