Hi! You could use content negotiation to achieve what you want > http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html >
No, that's not what I want. I'm actually looking for a way to lift my REST api to the same level as my Web UI. I have a completely working Web UI, that uses models or querysets to create, update, delete and list objects. Now, for a REST api I would create a shadow structure where I release resources, that are based on the same models or querysets I use in the Web UI. But I don't want to split these two. If I develop a new feature for the Web UI, it should be in the REST api as well. I want the REST api to be a first class citizen like the Web UI. Is there a way for the Web UI (which uses generic class based views) to rely on the REST api instead of the ORM? Is this possible with tastypie or whatever? Do you guys all separate the Web UI from the REST api? Or are you creating full Ajax-Web UIs, that are based on REST apis? Kind regards Dennis -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/8e58c872-875b-4e2a-bfd9-2ff226d4c3f3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
