| RE: What is Auto Event Fire up ? | ||
| AutoEventWireup is an attribute in Page directive. It's a Boolean attribute which indicates whether the asp.net pages events are auto-wired.When we set the value of the AutoEventWireup attribute to true, the ASP.NET runtime does not require events to specify event handlers like Page_Load or Page_Init.If we set the value of this attribute to true, framework must make a call to reateDelegate method for every Web Form (.aspx page). So it will be a performance issue and should not set the value to true if performance is a key issue. |
| | |||||||||||||||
It will set a value to false or true which tells whether the ASP.NET pages are automatically connected to the event handling functions or not.By default it will be set to False.If it is set to true handlers will be executed twice.
| |||||||||||||||
Related Questions
Latest Answer : Hai,Memory Management is a crucial role in every operating system. Memory management is there are many types such as 1. Storage memory Management 2. I/O Memory Management etc .. ...
DNA that is Distributed intrNet Architecture. It was an revolutionary concept that was developed by microsoft for delivering the n-tier architecture. Later it was suffered from backward compatiablitiy issues and then it gave birth to the .net technology which incorporatates the safer exection of code through CLR. DNA is also suffered with SIDE-BY-SIDE execution and improting and plumbing of code while executing the application into our server in asp3.0 but in .net it was completely revelaed and the problem was diagnoised. DMA makes and support the two tier and three tier to n-tier architecutre application in which it can be able to communicate and transfer the data as much as it can but pratically it was very difficult with "Windows DNA".
DNA that is Distributed intrNet Architecture. It was an revolutionary concept that was developed by microsoft for delivering the n-tier architecture. Later it was suffered from backward compatiablitiy issues and then it gave birth to the .net technology which incorporatates the safer exection of code through CLR. DNA is also suffered with SIDE-BY-SIDE execution and improting and plumbing of code while executing the application into our server in asp3.0 but in .net it was completely revelaed and the problem was diagnoised. DMA makes and support the two tier and three tier to n-tier architecutre application in which it can be able to communicate and transfer the data as much as it can but pratically it was very difficult with "Windows DNA".
| RE: how does the cookies work in asp.net? | ||
| we know Http is an state-less protocol which is required for interaction between clinet and server . so there is an need to remeber state of request raised by an web browser so that web server can recognize you have already previously visited or not. There are two types of state management techniques: a) Client side state management b) Server - side statemanagement Using cookies comes under clinet side statemanagement .In HttpResponse we write Cookie containing sessionId and other information within it. when a browser made a request to the web server the same cookie is sent to the server where server recognize the session id and get other information stored to it previously. Cons: 1)Cookie should contain non sensitive data as one can easily read cookies and they result of which your security may be tampered . 2) Cookie should not contain large amount of information as they are sent back and forth with request and response in between client and server which may cause your Performance degradation |
No comments:
Post a Comment