On Tue, 2008-11-11 at 13:47 -0800, David Cramer wrote: > Well I'm not sure storing multiple search paths is too good of an > idea, as you increase the size of the session significantly, and then > have to worry about expiring those or clearing them somehow. The > session just keeps it for that users session, vs whoever else happens > to visit that url (say I pass it off to a coworker).
This last point is exactly why putting it in the URL is the better solution. It's the whole idea behind addressable resources. You can then pass around the right filtered view to a colleague via email for further work. Or you can record it in an issue tracker. Or bookmark it to come back to later on. Storing it in the session would throw away all those benefits. We're developing for the web here; let's use the advantages of the medium, rather than doing all the work and then only making it available to the single person viewing it at that moment. Persistent filters makes sense; we should do that. But in the URL if at all possible, since it's best practice. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
