Hi, >I've been thinking about how Django might leverage DHTML^H^H^H^H^H >AJAX a lot recently, and I think the framework I'll sketch out below >should make a bunch of people happy.
my main gripe with your ideas is that you throw RPC style stuff (XML-RPC and SOAP) in with the REST stuff. That just doesn't compute - both are far too different in philosophy and structure to be really compatible with each other. I think we need two different things for webservices - support for RPC style APIs and support for REST style APIs. And both can be mapped into the ideas of Django quite nicely, I think. I have written down my ideas in my trac: https://simon.bofh.ms/cgi-bin/trac-django-projects.cgi/wiki/WebservicesForDjango I first thought about posting it here, but it got longer and longer and so I thought it's better to put it into one place and only post the link ;-) So my main problem is, RPC needs just one view func with registerable callbacks (and a set of predefined callbacks for models) that sits on one URI and dispatches on method name, while REST style APIs need a way to map objects into the url space (so the dispatch is done by the standard url pattern handling of Django). Of course everything on that page is just an idea - and it's written over a short period of time, so it's neither complete nor perfect. It might even be that some things don't make sense at all (like how the url space for REST APIs is structured - that's just an idea how something might look like, as that gives a more concrete thing to talk about). bye, Georg
