Thanks Malcolm and Rob.

The idea of calling get_myresource() at the end of post_myresource() makes a lot of sense in case POST needs to return the representation of the new resource. For some objects it may not be practical or desirable (heavy objects, complex queries, performance-sensitive APIs). So this one is clearly up the the application to decide.

Rob's idea of providing a generic dispatch method is very application independent, thus could be worthy of inclusion into the framework itself.

In any case, those ideas could be instrumental for implementers for http://code.djangoproject.com/ticket/115 (Models CRUD via web services)

Thanks,
Alexis


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to