GridView Sorting, Paging without using Session, ViewState or Cache

Hi,

Thanks for the comments, i was waiting for some discussions about static topics.
Because sometime its a difficult topic to understand, am still learning. :-)

You are right, the above article not saying this a final solution to avoid session, veiwstate etc.
But to an extend you can avoid those. If you are sharing same datatable/dataset across all users/sessions, then you can try above article.

This line will always reset the dataset and bind new updated records if needed.
 private static DataSet tmpds = new DataSet();
There will be always one copy of tmpds. I think this will not increase the variable/obects count in memory,
only the dataset will get refreshed with new records. If am wrong, please correct me.

But, if your datatable/dataset is different against every sessions then i will not suggest above article.
Static variable is not good to store user-specific data.

Also, you can change your logic in removing static variable (tmpSort) and use a Label control for storing sorting value.

<asp:Label ID="lbl1" runat="server"> DESC</asp:Label>
//private static String tmpSort = " DESC";
dataView.Sort = e.SortExpression + (string)((e.SortDirection == SortDirection.Ascending) ? lbl1.Text : lbl1.Text);
lbl1.Text = (lbl1.Text == " ASC") ? " DESC" : " ASC";

A Static variable has only a single lifetime, which lasts for the entire time your application is running.
Resetting of application pool or IIS reset will helps clear the data.

One other thought.  If your web application is running on multiple servers, you may have problems with static variables.  You may also have problems using the Cache, but that's a different issue.

I've seen articles about problems with static variables in IIS.  See for example http://sharenotes.wordpress.com/2010/01/07/static-variables-issue-in-shared-hosting-or-multiple-servers/ 

So again, I think it's a clever idea, but I don't think I would try it without a lot of testing on a server farm.