Awesome! I've been using django-oauth for sometime now, been looking at django-restapi and so on. But this takes the best of both worlds. And I especially like that it is not tied to the data models, so this means we can build in some business logic.
Basically, it's a bad idea to couple something like django-piston too tightly to the underlying models because in any even moderately useful API there will be plenty of resources you want to expose that are actually cobbled together from various different models (or even other storage locations such as a search index or external web service).
FWIW, I switch from django-rest-interface to django-piston. The models are very similar, but I think piston is a little cleaner. It also seems to be a little more actively developed (at least, according to the source histories).
Well, a lot of the requested changes now require a re-write. And I don't have time for it, unless a project comes along and requires just that. I am not sure what to do about it other than hope someone would help.
I was just looking at Django REST apis last night but didn't find this one. This seems really similar to django-rest-interface, except for the oauth. Anybody know the potential upside/downside to this versus djang-rest-interface?
"The Django REST interface makes it easy to offer private and public APIs for existing Django models."
Piston doesn't tie you to a model (although it can), which is very important for any decent sized API. Exposing models is something you want half the time, but there's a lot more to it.
