3 ms·
Also perhaps, is to choose Tastypie if you want API Key Authentication, and Django-Rest-Framework if you want oAuth. That's the reason I chose Tastypie over ev
by bmelton 15y ago
Also perhaps, is to choose Tastypie if you want API Key Authentication, and Django-Rest-Framework if you want oAuth.
That's the reason I chose Tastypie over everything else, but I really like the user-facing interface to Django-Rest better than I do Tastypie. Not enough to forego our preferred authentication-schema mind you, but I wouldn't hate having Class-based APIs either, but I haven't found that to be limiting in Tastypie either.
Also, there's a Tastypie implementation for Mongo floating around out there somewhere as well.
- pydanny 15y agodjango-rest-framework doesn't come with OAuth out of the box, django-tastypie does. ;-)
- bmelton 15y agoGah, you're right -- I was thinking of something altogether different. Thanks for the correction.
- gourneau 15y agoThis is a github issue to integrate TastyPie into Swagger https://github.com/toastdriven/django-tastypie/issues/422 https://github.com/toastdriven/django-tastypie/issues/422 Swagger creates beautiful interactive sandboxes for REST APIs http://swagger.wordnik.com/ http://swagger.wordnik.com/