You are presented with multiple paper abstracts, alongside the associated literature review and chapter titles. Given the provided information, you are going to do a literature review. Please generate a coherent literature review that synthesizes the content, draws connections between different works, highlights major findings, and identifies any gaps in the existing research.

Literature Review Title: Change Detection and Notification of Webpages: A Survey 
Chapter Title:  Categories of Change Detection and Notification 
1. Abstract of Cited Paper (BIB001):  The Internet at present has become vast and dynamic with the ever increasing number of web pages. These web pages change when more content is added to them. With the availability of change detection and notification systems, keeping track of the changes occurring in web pages has become more simple and straightforward. However, most of these change detection and notification systems work based on predefined crawling schedules with static time intervals. This can become inefficient if there are no relevant changes being made to the web pages, resulting in the wastage of both temporal and computational resources. If the web pages are not crawled frequently, some of the important changes may be missed and there may be delays in notifying the subscribed users. This paper proposes a methodology to detect the frequency of change in web pages to optimize server-side scheduling of change detection and notification systems. The proposed method is based on a dynamic detection process, where the crawling schedule will be adjusted accordingly in order to result in a more efficient server-based scheduler to detect changes in web pages.

Literature Review:
Based on the architecture involved, change detection can be segregated into two main sub domains. The first branch is "server-side change detection" and the other is "clientside change detection" BIB001 ]. Server-side change detection systems use servers which poll webpages, track changes and notify them to users. The client-side change detection systems make the client-side infrastructure poll the webpages and track changes on their own. CDN systems obtain webpage versions by crawling them and save the data to version repositories. This data is saved in an unstructured manner, mostly in the format of documents with tags, in order to allow easy storage and retrieval. Then changes are detected by comparing a previously saved version with the latest version of a particular webpage using similarity computations. Majority of the change detection mechanisms convert the data of a saved version in to a "XML-like" format where an element represents an "open-close HTML tag". Certain CDN systems allow the user to define a threshold of change, and the user gets notified about the changes, only if the change exceeds this threshold. Majority of the CDN systems operate on predefined monitoring schedules, which are specified by the user or determined by the system itself. Detected changes are visualized using many methods. A common means of visualizing text changes is by showing the newly added content in green color and the deleted text in red color (often with a strikethrough formatting) [Wachete.com 2014] . Another prominent factor discussed on CDN systems is their crawling schedules. Most of the currently available CDN systems crawl webpages under predefine schedules BIB002 ]. However, webpages can update at different time schedules (certain webpages may be frequently updated, whereas some webpages may get updated rarely), thus how often they change can vary from page to page. Hence, CDN systems require mechanisms for estimating the change frequency to create efficient checking schedules for webpages. This will reduce the number of page checks, where no changes were detected and maximize the probability of achieving optimum resource utilization.