I'd really recommend just using regular views and URL conf. Writing views 
explicitly, using renderers/parsers/permissions/authentication to set up 
your basic API policies, making use of serializers for data validation, 
etc... gives you plenty of value over using regular Django, while still 
keeping your view logic nice and explict.

You *can* use routers and viewsets, but it's typically over-complicated, 
unless you happen to be writing a CRUD-style API.

Cheers,

  Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django REST framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-rest-framework+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to