Master of Science (MS)
When a user explores different web pages in a given website, the website typically sends the entire requested page even if only a portion of the page was different to the current page. That is, two pages on a given website might share elements on the page like search bar, left bar, navigation controls, advertisements, etc., but this information is retransmitted. Most of the users spent their time on the front-end while downloading all the components in the page. Nowadays, server-side caching of page elements is often done using tools like memcached. The aim of my project is to explore element web page caching on the client-side. That is, our goal is to develop a system that caches the most common html parts of web pages in the website and reuses them in the further web pages reducing the transmission data. This effect probably is currently attainable using frames or object tags; however, the actual UI meaning of these tags is different than one integrated HTML file and so could cause usability issues, therefore, we want to explore solutions which are transparent to the end user -- the solution must behave just like a single fixed web page. In order to explore the advantage of having client-side caching and determine the effect on the response time, we made our server set-up as realistic as possible. So Squid, a front-end load balance, was used when we tested our client-side caching.
Karri, Ramya, "Client-Side Page Element Web-Caching" (2009). Master's Projects. 137.