Download : ASP.NET Questionnaire / PDF
Download : ASP.NET Questionnaire / PDF
Question: Why a conventional ASP web page is considered to be stateless amd how do u overcome this using ASP.NET?
Answer: Whenver a URL request is made, Web server creates instance of requested web form, generates HTML and posts it to browser for rendering. It then destroys instance of web form on the server. When user submits data back to the web server, a new instance of web form is created which has no knowledge of earlier webform. Hence conventional web page is stateless. In ASP.NET before web form get destroyed the state of the webform is stored in Viewstate(hidden control) on the page and when the page is posted back, the state of the webform is restored from view state.
Question: What is a web-farm and how do u manage session in web-farm?
Answer: A web-farm is group of webservers hosting a single web application. Sice the web application is shared across multiple servers, session info can not be stored in process memory of any of servers. It should be stored in a centralizes database or state machine.
Question: What is difference between following statements
1 - <%@ outputcache duration=”60” varybyparam=”none”>
2 - <%@ outputcache duration=”60” varybyparam=”*”>
3 - <%@ outputcache duration=”60” varybyparam=”name”>
Answer: Statement 1 caches only one version of the page irrespective of querystring
parameters. Statement 2 caches multiple versions of same page I any of
quewrystring parameter varies. Statement 3 caches multiple versions of the
page for different values of parameter xyz.
Question: What are 2 expiration policies for Cached objects?
Answer:
1. Absolute expiration: This is fixed duration expiration. For cache duration of 10 seconds, object is removed from cache after 10 seconds no matter what.
2. Sliding expiration: Canche duration varies based on frequency of access. E.g. If there is sliding expiration of 10 seconds and item is accessed from the cached again at 8th second, then object is reached again for the next 10 seconds.......
Download : ASP.NET Questionnaire / PDF
Question: Why a conventional ASP web page is considered to be stateless amd how do u overcome this using ASP.NET?
Answer: Whenver a URL request is made, Web server creates instance of requested web form, generates HTML and posts it to browser for rendering. It then destroys instance of web form on the server. When user submits data back to the web server, a new instance of web form is created which has no knowledge of earlier webform. Hence conventional web page is stateless. In ASP.NET before web form get destroyed the state of the webform is stored in Viewstate(hidden control) on the page and when the page is posted back, the state of the webform is restored from view state.
Question: What is a web-farm and how do u manage session in web-farm?
Answer: A web-farm is group of webservers hosting a single web application. Sice the web application is shared across multiple servers, session info can not be stored in process memory of any of servers. It should be stored in a centralizes database or state machine.
Question: What is difference between following statements
1 - <%@ outputcache duration=”60” varybyparam=”none”>
2 - <%@ outputcache duration=”60” varybyparam=”*”>
3 - <%@ outputcache duration=”60” varybyparam=”name”>
Answer: Statement 1 caches only one version of the page irrespective of querystring
parameters. Statement 2 caches multiple versions of same page I any of
quewrystring parameter varies. Statement 3 caches multiple versions of the
page for different values of parameter xyz.
Question: What are 2 expiration policies for Cached objects?
Answer:
1. Absolute expiration: This is fixed duration expiration. For cache duration of 10 seconds, object is removed from cache after 10 seconds no matter what.
2. Sliding expiration: Canche duration varies based on frequency of access. E.g. If there is sliding expiration of 10 seconds and item is accessed from the cached again at 8th second, then object is reached again for the next 10 seconds.......
Download : ASP.NET Questionnaire / PDF
0 commentaires: