| TOTAL: 10 Page: 1 of 1 |
|
Using Reflection Emit to Cache .NET Assemblies
There are few automated ways of caching methods within a Microsoft .NET Assembly or Web Service without writing a significant amount of the logic into the application. And sometimes, if the Web Service or .NET Assembly is from a third party, it isn't possible. This article outlines a non-intrusive caching solution that uses Reflection Emit in the Microsoft .NET Framework. Reflection Emit is the ability to generate assemblies, types, methods, and MSIL (Microsoft Intermediate Language) on the f
| Hits: | 32 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Ultimate Caching: Output and Fragment Options
With Beta 2 of ASP.NET, there are now quite a few options available for caching. Of course the first thing you should do to become familiar with caching is read up on it in the ASP.NET Quickstart Tutorials. Once you're throught there, though, come back here and let's go through some more examples of the different options available and discuss some of the potential issues with using each option. Output Caching In .NET Beta 1, output caching was great, but it had a few issues. For one thing, i
| Hits: | 40 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Page Data Caching
ASP.NET provides a full-featured cache engine that can be used by pages to store and retrieve arbitrary objects across HTTP requests. The ASP.NET cache is private to each application and stores objects in memory. The lifetime of the cache is equivalent to the lifetime of the application; that is, when the application is restarted, the cache is recreated. The cache provides a simple dictionary interface that allows programmers to easily place objects in and retrieve them from the cache. In the
| Hits: | 34 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Page Output Caching
Output caching is a powerful technique that increases request/response throughput by caching the content generated from dynamic pages. Output caching is enabled by default, but output from any given response is not cached unless explicit action is taken to make the response cacheable. To make a response eligible for output caching, it must have a valid expiration/validation policy and public cache visibility. This can be done using either the low-level OutputCache API or the high-level @ Outp
| Hits: | 41 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
.NET Data Caching
In simple terms data caching is storing data in memory for quick access. Typically information that is costly to obtain (in terms of performance) is stored in the cache. One of the more common items stored in a cache in a Web application environment is commonly displayed database values; by caching such information, rather than relying on repeated database calls, the demand on the Web server and database server's system resources are decreased and the Web application's scalability increased. As
| Hits: | 114 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Cache Control with ASP+
One of the classic ASP problems is in caching the output of a web page. ASP code is interpreted by the ASP.DLL file and there is nothing in the ASP architecture that allows caching. However, this is not the case in ASP+. In this article, Srinivasa Sivakumar explores the caching features added to ASP+ with the help of the .NET framework, and in doing so will give some examples obtaining data from both SQL Server and XML.
| Hits: | 32 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Using the Caching API in ASP.NET
Although there are many different ways to use the Caching API in ASP.NET, they all boil down to three distinct approaches. This discussion will outline these three approaches and demonstrate each of them in action. It will also give an example of the appropriate use of each approach. Absolute Expiration The first approach to using the Caching API is absolute expiration. What this means is that when you put a piece of data into the cache, you specify an exact time when that data will become
| Hits: | 52 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Cache Expiration Callbacks In ASP.NET
One of the greatest caching features implemented in ASP.NET is the ability to assign a callback function that gets fired when an item is removed or expired from the Cache. This article will explain how it all works, and show you how to wire up your own cache expiration callback. Cache removal callbacks are enabled through the use of the CacheItemRemovedCallback delegate. Delegates are how function pointers are implemented in the .NET Framework. Wiring up a cache removal callback involves 3 s
| Hits: | 109 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Caching Multiple Versions of User Output Control
Just as you can cache multiple versions of a page's output, you can also cache any or all possible versions of a user control's output on any given Web page. There are some differences, though, between adding user control output to the cache and doing the same for the page. While both support multiple response caching based on HTTP GET and POST parameters, user controls do not support caching based on HTTP headers or custom strings. Basically, ASP.NET allows caching multiple versions of
| Hits: | 36 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |
Caching in .Net
One of the new features in ASP.NET is a system for caching page and application data, so that you don’t have to perform the same expensive process every time someone views a page. Page caching: Caching can be performed on a per-page basis, or on a per-user-control basis, letting you store part or whole pages in a cache, and customise their expiration. Page caching is controlled by the <%@ OutputCache %> directive (search for output caching in MSDN), which has two compulsory parameters:
| Hits: | 74 | Platforms: | Windows |
| Ratings: | Last Updated: | 2006-07-11 |