Hello Zopistas I have been running a Zope site for a couple of months using the ZopeHTTPServer. Unfortunately the server crashes occasionaly with no informative comments in the var/server.log. Has anyone else encountered a similar situation? I am waiting for the medusa integration. A bobo app I was running over medusa proved to be very reliable. A month ago I was contemplating implementing Userland's XML-RPC protocol in python, and yesterday I noticed Fredrik Lundh posted a module for it. It is a very simple RPC protocol different from bci (oops ZClient) and it might be useful to integrate it into the forthcoming medusa server. Skip who seems to have taken note of it already might provide some useful info. Pavlos
Pavlos> A month ago I was contemplating implementing Userland's XML-RPC Pavlos> protocol in python, and yesterday I noticed Fredrik Lundh posted Pavlos> a module for it. It is a very simple RPC protocol different Pavlos> from bci (oops ZClient) and it might be useful to integrate it Pavlos> into the forthcoming medusa server. Skip who seems to have Pavlos> taken note of it already might provide some useful info. Yes, I have been trying it out. I plan to use XML-RPC to replace the ad hoc encoding scheme I'm currently using. The main attractions for me are: * it is language-independent, offering at least Python, Perl and Frontier interfaces (it was developed by Dave Winer at Userland, the Frontier folks) - I need access from both Perl and Python. * it was extremely easy to get going, especially after Fredrik Lundh (who wrote the Python library) sent me an under 40-line server. * I get to throw away some homegrown code (don't laugh). If you'd like to try it out, grab Fredrik's xmlrpclib module from http://www.pythonware.com/madscientist/ install it, then execute import xmlrpclib s = xmlrpclib.Server("http://dolphin.calendar.com:8000") print s.latlong("San Francisco", "CA") print s.latlong("Stockholm", "", "Sweden") try: print s.latlong("Spam", "", "Eggs") except xmlrpclib.Fault, fault: print "oops...", fault.faultString which should display [37.775, -122.418333] [59.3833, 18.0] oops... No latlong for (Spam, , Eggs) that is, you get lat/long coordinates back for the first two cities and a catchable fault response for the third. I'm not really in a position to compare XML-RPC and ZClient and I can't seem to get to www.zope.org at the moment to do any reading on ZClient. Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ skip@calendar.com | Musi-Cal: http://concerts.calendar.com/ 518-372-5583
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 ZPublisher. 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 -- 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.
participants (3)
-
Jim Fulton -
Pavlos Christoforou -
skip＠calendar.com