On 6/12/07, John Goodleaf <[EMAIL PROTECTED]> wrote: > > Nevermind. I got it. I missed that _all_ requests should be forwarded to > handle_xmlrpc. I was expecting the registered ones functions to behave > "normally." Well it was actually your email that tipped me off, but > let's chalk it up as an object lesson on reading code. (For anyone > unfamiliar, the code states clearly that requests should go > handle_xmlrpc. My bad.) I coulda solved it with a little more reading. > And coffee. > > Thanks Graham. I look forward to using this xmlrpc interface since it > hits the sweet spot for my present needs. Simpler than SOAP, less > cutting edge than REST. > If you like you can see one middleware that I wrote before.
http://www.djangosnippets.org/snippets/71/ It's not need to bind all xml-rpc methods into one handler, you can invoke xml-rpc method through common url, only need to follow "?format=xmlrpc", so the request and response will be convert to xml format. But if you want to use this middleware, you should return pure data but not a real HttpResponse, and the middleware will automatically convert the pure data into xml format. Please see the description in the page. And I should say, I'v not been playing with this snippet for a long time. :) -- I like python! UliPad <<The Python Editor>>: http://wiki.woodpecker.org.cn/moin/UliPad My Blog: http://www.donews.net/limodou --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
