While I can't really comment on the thoughts of the Django team itself
(for inclusion in Django proper), I will suggest that aside from
Tastypie the other 'best-of-breed' REST framework is the simply-named
Django REST Framework: http://django-rest-framework.org/.
As opposed to Tastypie, it has one truly killer feature, IMHO: their
Resource/ModelResource classes provide an automatically-generated HTML
documentation for the exposed API. Browse the API's endpoints and it'll
tell you how to interact with it using JSON or XML.
On 1/6/2012 6:31 PM, Brett Epps wrote:
I used Tastypie for a project recently and was pretty happy with it. I
think Piston was the preferred package before Tastypie came about, but
Piston hasn't seen as much development recently. Then again, Piston seems
to be good enough for Bitbucket, so it's probably good enough for many
projects.
Sorry I can't offer much technical advice on this topic, as I'm no expert
on either package. To answer your question, though: to me, Tastypie
"feels" like the preferred package currently.
Brett
On 1/6/12 3:25 PM, "JohnA"<john.armstrong....@gmail.com> wrote:
Iąve looked on this group, stackoverflow and the web at large for
indication that the django community is converging on a single REST
API package that is łpreferred˛ and a potential candidate for
inclusion in a future django distribution. So far all Iąve seen is
people saying positive or negative things about various packages or
the alternatives of writing yet another package or just winging it
with urlconfs and views.
It doesnąt seem to be a matter of "it depends what you want to
do" (though maybe required use or not of HTTP PUT and DELETE methods
could be a deciding factor). Iąm not an expert in REST, but the basic
requirements seem pretty clear to me clean urls, multiple output
formats (xml, json etc.) and reliable and reasonably nonintrusive
authentication procedures plus of course ease of implementation
including achieving wide coverage of base functionality with minimal
incremental code.
I guess what I'm asking is, what if any REST API package is emerging
as the leading solution, and if none, why not? Thanks.
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
--
David W. Harks<d...@dwink.net>
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.