Have you looked at REST<http://en.wikipedia.org/wiki/Representational_State_Transfer> style URI's? With REST the action (aka verb) is never contained in the URL and is instead enumerated by the HTTP method type (ie: GET, PUT, POST, DELETE). This produces a much cleaner, more useful, more straightforward URI. It would look more like:
Method Type: URI GET <data_type/<ID> PUT <data_type/<ID> POST <data_type/<ID> DELETE <data_type/<ID> There are also some challenges when implementing REST too, but I just wanted you to be aware of it. Brian On Wed, Sep 22, 2010 at 7:20 AM, jayfee <[email protected]> wrote: > so i'm using django to do some "CRUD" type stuff, but i'm avoiding > using the generic create_update methods because i've found my > relationships and data types don't always fit neatly enough to work. > anyway, the piece that i'm trying to tackle now is getting a clean > routing system going. here's how i'd like it to work: > > urls are formated like: > > <data_type>/<CRUD>/<ID> > > id is optional. examples: > > /person/create : create a new person > /place/update/2: update an existing person with id 2 > /thing/delete/2: delete an existing person with id 2 > > i wonder if there are any examples floating around that talk about > this pattern and cleans ways to implement it as far as the routing > portion goes. > > -- > 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]<django-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Brian Bouterse ITng Services -- 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.
