i'm not having a specific problem, although i will present one to you:
i have a database-bound webform with a simple sortable datagrid on it. when a user sorts by clicking on a header, the sort event handler is fired, a posback is done, and the net result is the grid is re-databound with the data sorted in the desired way.
the problem here though is that a user cannot refresh (by hitting 'f5' or 'ctrl-r') without being prompted to re-send this information (post again).
to me, this behavior is undesirable. i'd like the user to be able to refresh whenever he wants without having to re-send information. the only way i can think of doing this is to do so using response.redirect in the event handler.
how about i run two ideas i had by you:
1) use the querystring- while certainly not the most elegant, i could pass sorting information in the querystring (and in whatever format i choose, whether that be one 'sortcriteria' name-value pair or multiple). if this were the case, the onsort handler would call response.redirect to the same (current) page, but would also be responsible for setting the appropriate querystring values.
2) use session variables- i still don't know if it's considered 'bad practice' to use session variables, but instead of redirecting and using the querystring, the sort handler could set some session variables (ie Session["sorttype"] = "hitsdesc") which would need to be passed into the databind on page_load and handled appropriately.
i'm not trying to do things in a classic asp way. in fact, i LIKE the asp.net model much better. but there are a few minor details such as this that stick out. your feedback & thoughts are greatly appreciated. what do you think of this?