Jim> I think that XML-RPC would almost certainly be a cool thing to Jim> support in Zope, and Zope would be a cool server for XML RPC. IMO, Jim> the right way to do it would be to add support for it to Jim> ZPublisher. Yes, and Dave Winer would like to see Zope support XML-RPC. I could add it easily to the module I'm currently publishing. I'll see what I can come up with. It's perhaps not what Jim had in mind, but should be easily incorporated into other peoples' servers. Jim> XML-RPC (http://www.scripting.com/frontier5/xml/code/rpc.html) uses Jim> POST requests with content type "text/xml". (Does anyone but me Jim> think that this content type is a bit too broad?) I suspect on the surface it might be. I'm no whiz with HTTP, but XML-RPC requests are supposed to POST to /RPC2: POST /RPC2 HTTP/1.0 Content-type: text/xml ... I think that should serve to distinguish between different uses of text/xml, yes? I noticed with my sample server (the stuff Fredrik Lundh sent me) I am seeing all of POST /RPC2 HTTP/1.0 POST / HTTP/1.0 GET / HTTP/1.0 I'm not inspecting the PATH component at the moment, so the first two both work. The second should get a 404 error since my server only handles XML-RPC requests. The third bombs correctly with a 501 error (method not implemented). Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip@calendar.com | Musi-Cal: http://concerts.calendar.com/ 518-372-5583
skip@calendar.com wrote:
Jim> I think that XML-RPC would almost certainly be a cool thing to Jim> support in Zope, and Zope would be a cool server for XML RPC. IMO, Jim> the right way to do it would be to add support for it to Jim> ZPublisher.
Yes, and Dave Winer would like to see Zope support XML-RPC. I could add it easily to the module I'm currently publishing. I'll see what I can come up with. It's perhaps not what Jim had in mind, but should be easily incorporated into other peoples' servers.
Jim> XML-RPC (http://www.scripting.com/frontier5/xml/code/rpc.html) uses Jim> POST requests with content type "text/xml". (Does anyone but me Jim> think that this content type is a bit too broad?)
I suspect on the surface it might be. I'm no whiz with HTTP, but XML-RPC requests are supposed to POST to /RPC2:
POST /RPC2 HTTP/1.0 Content-type: text/xml ...
That was just an example. XML-RPC says: "The format of the URI in the first line of the header is not specified. For example, it could be empty, a single slash, .... we allow the URI to help route the request to the code that handles XML-RPC requests." For Zope, the URI should point at a Zope object.
I think that should serve to distinguish between different uses of text/xml, yes?
Nope. Jim -- 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 repeats.
Skip> POST /RPC2 HTTP/1.0 Skip> Content-type: text/xml Skip> ... Jim> That was just an example. XML-RPC says: Jim> "The format of the URI in the first line of the header is not Jim> specified. For example, it could be empty, a single slash, .... Jim> we allow the URI to help route the request to the code that handles Jim> XML-RPC requests." Oops, my mistake. That's what I get for just looking at the pictures... ;-) Still, a URI plus a content type should be enough to decide you're going to be processing an XML-RPC request, right? Presumably you won't have the same combination of URI and content type meaning two completely different things. Still, if "text/xml" as a content-type isn't sufficient, perhaps we can prevail upon Dave Winer to add a parameter to the content type, e.g.: text/xml; service=XML-RPC Is this what you had in mind? Skip
On Fri, Jan 22, 1999 at 02:14:04PM -0500, skip@calendar.com wrote:
Still, if "text/xml" as a content-type isn't sufficient, perhaps we can prevail upon Dave Winer to add a parameter to the content type, e.g.:
text/xml; service=XML-RPC
Is this what you had in mind?
Why not use text/x-xml-rpc? XML has a billion uses, that honestly, it will eventually end up as: xml/rpc instead, most likely :-) What's the status of text/xml as a standard MIME type? Chris -- | Christopher Petrilli | petrilli@amber.org
participants (3)
-
Christopher G. Petrilli -
Jim Fulton -
skip＠calendar.com