Hi Matt,
I think your form should use GET method, not POST method: there is no
modification implied when submitting it.
Now, I'm perfectly fine using parameters in the url as it is meaningful:
your accessing the search ressource and passing it a parameter. It's
different for a ressource that should be tight to some content, like a
post on a blog where the url is set "dynamically": the ressource exists
or not.
Another case where I asked me the question of "clean url" was
pagination. Here again, I'm confortable with "unclean" url (you can pass
a number of occurences per page and the page number you want to access).
Well you must handle "unranged" pages...
About redirection, I'm not sure, but this can trouble navigator's
previous page (why redirect after a successful POST if it doesn't :).
In real world, I you search for a keyword and you get only one match,
then you can be redirect to the only result details page, so you're
redirection cannot be blamed, but this is done more for user experience
than purity concern.
OK, I'll understand if that don't help you but maybe some experienced
people can react ^^
Regards,
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To post to this group, send email to django-us...@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.
