in my opinion no, it actually makes sense to have an API with its own routes and views.
I suggest you take a look at tastypie or DRF On Thu, Feb 12, 2015 at 10:17 AM, Aaron Reabow <[email protected]> wrote: > I would like to separate out my ajax requests into their own views (one > per page, is what I am thinking) > > This allows me to keep a very generic base view that applies to multiple > pages. This have a number of advantages for me, such as building a bullet > proof view that never gives any trouble :) > > Really what I am asking is - from a conceptual level, are their any > serious reasons why this approach would be a bad idea? > > (I am just taking my first steps into the world of ajax, hence the > beginner question) > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/f714b07b-ad69-4e60-8ce4-3cc73cc85cea%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/f714b07b-ad69-4e60-8ce4-3cc73cc85cea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6t%2B_TFiBGyHjcLgtt0hVaZ3mmZYbO64nvBnvUiMN90UjBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
