Skip to main content

70-562 Caching




Caching is to improve performance, caching pages and framents, and also data can dramatically improve the performance of a website.

The only cachin in classic asp were variables, and it's usefullness was very limited.

Now, in asp.net, there are mutliple type of caching.

1)Caching pages and user controls by the OutputCache directive, for how long and how many version are kept
2)Caching from code, more control than by page, but only used if it needs to change at run time.
3)Caching data, data storage is always in process, dataset, arrays, custom objects, similar to store in sessions state, but application wide, can determine how long the object in cache, and the cache can be flushed when the memory gets low.

Retriving a page from the cache is much faster than regenrating the page.

Static pages need to be cached as they dont change, for pages that do change, mutliple versions can be kept.

As a simple tutorial, output the page directive and it's duration in seconds, VaryByParam allows to specify which version based on a value of the param, Common.GetOutputCacheDirective(Server.MapPath(pageFileName));

You can encode those params as query string, or form values, it's possible to use * for all the parameters on teh page, or many params sepecated by a semicolon-demilmited list.

If asp.net finds the right combination of params in the cache, it uses it, otherwise, builds the page.

The params can also be the IDs of the controls on the form.

The HTTP header can also be used to identify page variations. VaryByHeader="Referer" in the page directive allows to vary by the caller(the calling page).

VAryByCustom can be used to vary by browser. In the global asax it's possible to override the GetVAryByCustomString value, which can be used for testing browser versions.

Comments

Post a Comment

Popular posts from this blog

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

70-562 Custom Visualizers

Framework objects are clearly viewable in the locals window during debugging. User made class librairies and their object need to provide visualizers for maintenance and debugging. You can create your own visualizers, MS exposes the functionnality through the .Net Framework; and this is relatively easy. Mulitple visualizers can be created per type. You can have tree views, grids; customizing it to the way that is the most usefull for debugging this particular object. The [Serializable()] attribute has to be included to your class to allow the visual studio visualizer to parse the object. A visualizer is a dll, a regular assembly, it requires a windows form to display the data. The visualizer class will be implemented by the form. The visualizer class has to inherit the DialogDebuggerVisualizer class with the DebuggerVisualizer attribute, and also the Microsoft.VisaulStudio.DebuggerVisualizers namespace. The visualizer can be made to only read, or modify existing data. T...
Post a Comment
Read more