Here are the advantages and disadvantages I see myself: > 1. One of the approaches is to use special symbols for the controlling > words, which are not allowed in slugs, like in last.fm or wikipedia > does. (+) url rules for the app might be defined in a separate file (+) shortness (-) unusual/unnatural
> 2. Another way is to use a special symbol like a dot together with the > primary key as a part of the url for product-details page (+) url rules for the app might be defined in a separate file (-) IDs shouldn't be shown to people (technologies should serve real live but not vice versa). > 3. Using a prefix for product details (+) url rules for the app might be defined in a separate file (+) shortness (-) unnecessary not humanized wording > 4. Using a separate namespace for product details (+) url rules for the app might be defined in a separate file (+) clean naturally-looking separation (-) URL is long (-) where would /products/product/ lead? > 5. Using upper case for controlling words (+) url rules for the app might be defined in a separate file (-) weird and shouting too much > 6. Using plural for managing lists and using singular for managing > details (+) url rules for the app might be defined in a separate file (+) naturally conceived (+) shortness (-) where would /product/ lead? (-) requires two files for url rules if the urls are defined in each app mentioned in: http://www.xml.com/pub/a/2005/04/06/restful.html > 7. Using the controlling words before the type of list: (-) some urls look realy weird (-) can't be used in the app level --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
