Data Persistance with session variables or url variables

[ice78991]

I am designing a master/detail set of pages. A user fills out a form and the query results are shown in the master page. Click a link in the master page to see the detail page.

The problem is I want a prev/next link in the detail page which will involve submitting another query. How should I best preserve the query criteria from the original form page. I could use session variables or maybe store them in a url string which I add to each link. Security is not a major issue here. I can validate the form data before querying with it

So what's it to be. Sessions or urls ? ( hidden form fields are not an option here)

 

[ice78991]

I was thinking that maybe using urls will save me from excessive locking and will also save on RAM. I was hoping this would give improved performance. I notice that google advanced search uses urls to hold query information

 

[ice78991]

Well from having done some more research, I've decided that heavy use of session variables in an application is probably not a good idea.
I read an article by Ben Forta in which he states

In other words, locks can arbitrate code execution across multiple threads, pausing execution as needed. And yes, this could slow down your application, but considering the alternative it's a small price to pay

Full article :

http://www.adobe.com/devnet/server_archive/articles/locking_in_cf.html

I also read that session variables create a number of issues in clustered environments. So I shall be using urls to persist non sensitive data.