Yeah, i'll be taking the best out of every hint! The big problem is that the user has a lot of freedom. If he just wants to search for "barber" he can and urls will be /barber/ <whatever>/... Every parameter is optional, they're just bound to an order, if they're all present... So i don't have a "special" case (as the city-only) i can deal with easily :(
On Aug 10, 4:29 pm, Reinout van Rees <rein...@vanrees.org> wrote: > On 10-08-11 15:50, samuele.mattiuzzo wrote: > > > I was considering the option/country/italy/city/milan/job/engineer/, > > it wasn't that bat, but i'm risking very long urls if 4-5 parameters > > are set... > > If /italy/milan/barber is the normal url, by all means use that. > > The other scenarios can then get a longer url, like > > /city/milan > > This makes the city-only scenario distinguishable from something that's > a county+city combination. That way your regular urls stay nice and > short. Best of both ways? > > Reinout > > -- > Reinout van Rees http://reinout.vanrees.org/ > rein...@vanrees.org http://www.nelen-schuurmans.nl/ > "If you're not sure what to do, make something. -- Paul Graham" -- 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.
