Beside using the Comet technology, the problem can be solved by other means too, such as using plugins installed in the users’ browser to facilitate duplex communication. By offering real socket-based communication, these plugins make the dialog between client and server much easier to handle. Using plugins requires that they are installed previously in the client browser. Some users are not capable to do this for various reasons, which means a significant drawback for the solution. Another important issue is that the support for available plugins is weaker than the support for basic web technology. These circumstances mean that though plugins offer a great method to reduce the complexity of client-server communication, the technology is simply out of reach for a big chunk of web users.
WebSockets, which is part of the yet unfinished HTML5 standard, is a promising tool to replace Comet technology. The solution aims to provide a general and easy to use API to solve the problem of one sided client-server Ajax communication. The finalization of the WebSocket specification is currently hindered by security issues.
Considering the problems with browser plugins and the immaturity of the WebSockets technology, it is advisable to examine Comet techniques that implement duplex communication via using widespread browser technologies. My goal was to study the general Comet principles and implementations with their ASP.NET specific implications. Based on this knowledge, I had to build a framework which simplifies the usage of Comet. The framework’s abilities should also be demonstrated by a simple demo application.