Nis Jørgensen wrote: > As others have said, you can stuff things into request.session (after > adding the right middleware incantations).
Using the session middleware looks far better but it will take me a while to try that out. I'll try and do that next week. > What is so bad about leaving the url in the browser? I assume the error > message you display is the "correct" response for that url. Just > remember to add the correct status code - probably 400,403 or 404. Note > that if this is a GET url, it shouldn't have side effects, so your > "main?delete=100" example seems like a bad idea to begin with (unless > this is the page that shows an "Are you sure ...?" message). If it is a > POST, there is a lot of reason not to redirect it, since this will make > it harder for the user to use the back button to fix things. Yes its a GET that changes the database and I should look at that and change "main?delete=100" to main/del/100/ or something and make it a POST. And yes if I make it a POST I hadn't thought about users using the back button - which the will do :-( Thanks for this advice, and to Patrick for how he does things. Mike --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
