bodom_lx at task3 dot cc|

While searching for solutions on adopting Django for the server side of our Dynamic Car Pooling system, I found two very interesting projects:

• WAPI - a framework which abstracts the details involved in publishing an API and translates class methods to API methods, serializing the objects returned when possible. WAPI handles authentication, too, and other advanced functions. It's an amazing, fully Django compatible system that currently works over ReST (JSON, XML, YAML) but not with XML-RPC. Therefore, I contacted the author to have some information about the status of the project. It would be very interesting in our system, to provide API and XML-RPC services just by using his layer
• RPC4Django - provides XML-RPC and JSON-RPC support to an existing Django project. It promises a XML-RPC interface by just adding the decorator @rpcmethod to an existing python function. It also fully integrates with Django authentication framework

I'm going to experiment with these two tools. Obviously the first one is the most interesting because of its ability to "export" services in more formats. But the most important protocol for us is missing. Let's hope it will be added soon!

Tags: api, contact, django, DyCaPo, dynamic, Experiment, HTTP, pro, project, projects, promise, protocol, python, python django, rest, Serv, server, server side, sid, site, Status, web, xml-rpc

This entry was posted on Tuesday, November 10th, 2009 at 23:14 and is filed under Carpooling Research, Free*, Programming. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.