Hi,
We are developing a web portal that will be deployed in Web Farm. I would like to know if there will be any issues with paging in WebGrid in a web farm scenario, as for a given user session different requests can be served by different web servers in a web farm
i.e when i click on say Page 1, the request may go to webServerOne and on clicking on Page 2 the request may go to a different web server say webServerTwo
I would like to know if you foresee any issues in the scenario mentioned above, It will be nice if you can also detail how paging is handled internally
Regards,
Subodh
Kind of hard to answer this but I will give it a shot.
A lot of this depends on how you have your logic setup for example if you are using the session state to store user information and are not using sql or some other means for storing your session state then when you go to pull your data for the grid (ie: select * from users where account='fred') then it will not work because your session state will be on the server.
If you are using cookies and your load balancer maintains the cookie state then it will work fine.
If you are using Session State inside SQL and/or File on shared fileserver then it will work fine.
If you are using QueryStrings then it will work fine.
The grid itself works just fine in a web farm senerio this more has to do with your programming logic and server setup. You should be fine with the grid itself.
Keep in mind when doing web farm stuff you need to really maintain the viewstate (if you use it) so you really need to pay attention to how you are storing session information etc.