Data Cache from Classic ASP to ASP.NET{3}


by Antonio M
This article talks about Data Caching and the different kinds of caching techniques that a
web developer can use. In a nut shell caching is when data is stored “in memory for quick
access”. When data is cached the demand on the web server along with its resources are
decreased to allow for faster access to a web page. Caching is also used to retain the pages
and data across a HTTP request and has the ability to be reused. The author also talked about
the differences of Classic ASP and ASP.NET 2.0 (during the time of this article). In classic
ASP.Net there wasn’t anything as sophisticated as the ability to cache data using the catching
API in as in ASP.NET. The way that classic ASP would cache its data is through the use of
session, application and cookie objects. Cookie objects are stored in a  users browser and
are about 4,096 bytes containing only string information. The problem with this is that some
user can configure their browsers to no accept cookies. Session variables are also used to
cache info, each session variable is specific to a particular user. The disadvantage with this
is the same as cookies, the users browser must be configured to accept them. As for application
variables, they can be used globally for the entire web application. As for caching in ASP.NET 2.0
it still supports the ability to cache through using cookies, session and application variables but
now their is a data cache API. With this new API if server memory becomes scarce data that has
been cached can be removed to free up space and cache dependencies can be assigned. The author
further shows examples of you can use the Cache API in web applications to further enhance a users
experience.

I think this relates to the class because it talks about caching data in ASP. I also believe that
it would be helpful for students to have a brief history of how Classic ASP used to cache its data
prior to the cache API.

I liked this article due to that fact that it talked about cacheing. I had never really had any
experience in cacheing so this was all some what new to me. Even though this article is outdated
I would assume that the cache API is still in use today with the current ASP.NET. I am still not
too sure of the capabilities of data caching and would like the opportunity sometime in the future
to be able to work on an application that will allow caching. Overall it was an informative article.

Reference:
Gut, A.; Miclea, L.; Hoka, I.; Duma, D.C.; , “Custom technique for handling data caching in ASP.NET 2.0,”
Automation, Quality and Testing, Robotics, 2008. AQTR 2008. IEEE International Conference on , vol.3, no.,
pp.359-364, 22-25 May 2008
doi: 10.1109/AQTR.2008.4588944