What is the difference between normal browser caching and ASP cache object? How do they differ? -


I am starting for ASP. Net caching concept

What is the difference between normal browser caching and ASP cache object? How do they differ?

Why do we need to separate the cash? Will not this break the memory overhead?

ASP Net is capable of doing so in many ways You can specify that page in the browser or in your application domain to cache.

Normal browser caching or page caching refers to caching the object in the browser's cache so that the next request for the same page is locally served by a page browser, proxy server , The application server or many of these can be cached in the request. To set up a page's cacheability, see this article:

Where ASP has a cache object, .NET has created a per domain domain. This is an in-memory cache that can be used for archiving sessions or for any other object caching purpose, such as caching data loaded from the database etc. Note that this is an in-memory cache (as hashtable in the program), any data stored in this cache will be available only for that application.

Why do we need to break a cache? Will not this break the memory overhead?

The memory in the cache will cause memory overhead, but caching is always used to improve performance at the cost of memory. For example, instead of loading similar data from one database to each request, the data can be loaded into the cache, and all subsequent requests can be cached, thus improving functionality and loading on the database server To reduce

Browser caching and in-memory caching, many outputs of process, design caching solutions such as ASP Net Display are also available to boost performance and to overcome limitations in ASP.NET caching options. You can see more details here:

I hope this will be helpful :)

Comments

Popular posts from this blog

ios - Adding an SKSpriteNode to SKScene from a child SKSpriteNode -

Matlab transpose a table vector -

c# - Textbox not clickable but editable -