Malcolm, Thank you for your thoughtful reply, although I think its going to take me several re-readings to get a handle on it all. If I have the gist of it, it sounds like you're saying that a good design based on a thorough understanding of REST and a few conventions or best practices using the capabilities that Django already provides may be a simpler way to achieve the same goal? I have to admit that throughout working on this, I have wondered, and still wonder, if that isn't the better approach.
I also just want to make sure I haven't misled anyone about what I think I am doing--I am just learning both Django and REST, and fully admit that this work has been a stretch for me on both fronts. In fact, a large part of my motivation for blogging about this and writing the contribution was to elicit exactly the kind of response you gave. In my research into how to design a human facing Web application RESTfully, I haven't found a lot of explicit, practical information about how to do this. (Either that, or I just didn't understand it when I saw it.) In particular, I think your characterization here is right on the money: > Your approach to providing an interface for model CRUD-related methods > looks reasonable and non-repetitive for the user, but I wanted to make > clear that I think that's what you have done, not any kind of solution > to "how to fix REST in Django" (which would beg the question, for a > start). In struggling to understand REST, models and their related forms were the most obvious group of "nouns" I could see, and that's what ultimately led me to Charlie Savage's blog post on a RESTful Rails controller, which was a big inspiration for this work. As a result, I did quickly focus on model CRUD related methods, but I recognize this is only addressing one possible aspect of REST. (That's why for example, I didn't feel like I could replace all urlpatterns with the ones I was creating.) I also want to be clear that I didn't start this because I think Django is broken in any way, nor would I presume to be the one to fix it even if it was. I am actually really jazzed about Django (insert groan here) and REST too, and wouldn't be spending my time trying to understand how to do this if I wasn't. But ultimately, this contribution is me thinking out loud about these issues, and I won't be surprised to learn that I got a lot of it wrong. So, with all that weaseling out of the way, let me just say again that I appreciate the time you took to look at what I did and correct some of the misconceptions I have. I hope you do get a chance to look at the code for the contribution and let me know if you think there is something worth salvaging from this. adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
