I have a web application that uses a web service. A search is done on the main page — by passing parameters to a specific web service method, and I bind the results to a gridview.
I implemented sorting and swapping on a grid. By placing data that is bound to the grid in the view, and then, if necessary, reading / sorting / filtering them - and bandaging the grid.
Since the amount of data returned from the web service has increased dramatically when I try to search / sort, etc., I get the following errors.
The connection was reset
The connection to the server was reset while the page was loading.
I searched around a bit, and it seems that a very big idea is to blame. But, of course, the only option is
- Limit Results
- Hold data in a session, not in a view
- Something else i don't know about
I used to have a data type in the session, as some of this data had to be saved from page to page - (but was not published, so viewstate was not an option). As the amount of data increased and the need to save was removed, I used viewstate instead. To think that this was a better option than a session because of the amount of data that the session was supposed to hold and the number of users using the application.
Probably no.
I thought that when the viewstate turned out to be very large, this .net split it into more than one hidden viewstate field, but it seems that all I get is one mammoth view that I have problems viewing in the source.
- , , ? ?