|
|
| What are benefits and limitations of using Cookies? |
|
|
Following are the benefits of using Cookies:
No server resources are required as they are stored in client.
They are light weight and simple to use
Following are limitations of Cookies :
Most browsers place a 4096-byte limit on the size of a cookie, although support for 8192- byte cookies is becoming more common in the new browser and client-device versions available today.
Some users disable their browser or client devices ability to receive cookies, thereby limiting the use of cookies.
Cookies can be tampered and thus creating a security hole.
Cookies can expire thus leading to inconsistency.
|
|
| What is Query String and What are benefits and limitations of using Query Strings ? |
|
A query string is information sent to the server appended to the end of a page URL.
Following are the benefits of using Query Strings:
No server resources are required. The query string containing in the HTTP requests for a specific URL.
All browsers support query strings.
Following are limitations of Query Strings :
Query string data is directly visible to user thus leading to security problems
Most browsers and client devices impose a 255-character limit on URL length.
|
|
|
| What is Absolute and Sliding expiration? |
Absolute Expiration allows you to specify the duration of the cache, starting from the time the cache is activated. The following example shows that the cache has a cache dependency specified, as well as an expiration time of one minute.
Cache.Insert("announcement",announcement,depends,DateTime.Now.AddMinutes(1),Nothing)
Sliding Expiration specifies that the cache will expire if a request is not made within a specified duration. Sliding expiration policy is useful whenever you have a large number of items that need to be cached,because this policy enables you to keep only the most frequently accessed items in memory.
|
| What is cross page posting? |
By default, button controls in ASP.NET pages post back to the same page that contains the button,where you can write an event handler for the post. In most cases this is the desired behavior, but occasionaly you will also want to be able to post to another page in your application. The cross page posting feature in ASP.NET 2.0 allows you to fire a normal post back to a different page in the application. In the target page, you can then access the values of server controls in the source page that initiated the post back.
To use cross page posting, you can set the PostBackUrl property of a Button, LinkButton or ImageButton control, which specifies the target page. In the target page, you can then access the PreviousPage property to retrieve values from the source page.
|
| Can we post and accessview state in another application? |
You can post back to any page and pages in another application,too. But if you are posting pages to another application, the PreviousPage property will return null. This is a significant restriction, as it means that if you want to use the view state, you are confined, for example, posting to pages in the same virtual directory. Even so,this is a highly acceptable addition to the functionality of ASP.NET.
|
| What is SQL Cache Dependency in ASP.NET 2.0? |
SQL cache dependencies is a new feature in ASP.NET 2.0 which can automatically invalidate a cached data object (such as a DataSet) when the related data is modified in the database. So for instance if you have a dataset which is tied up to a database tables any changes in the database table will invalidate the cached data object which can be a dataset or a data source.
|
| What is Post Cache substitution? |
Post cache substitution is used when we want to cache the whole page but also need some dynamic region inside that cached page. Some examples like QuoteoftheDay, RandomPhotos, and AdRotator etc. are examples where we can implement Post Cache Substitution.
|
|
|
| Prev |
Main Page
DotNet