Web2Test is a tool for functional system tests of web based applications, portals and complex websites. Tests are platform and browser independent and tolerant towards layout changes. In addition web2test offers a real user simulation for a 100 % AJAX support. The test tool can be used under Windows as well as under Linux. The new release of itCampus’ test software for automated GUI tests of web applications – web2test – supports besides Internet Explorer 6, 7 and 8, Mozilla 1.8, Seamonkey 1 and 2 Beta and FireFox 2 and 3 already the newest FireFox version 3.5. Continue reading »
Ajax killed the click-and-wait experience we once associated with the Web and today, Comet is eliminating the stale data-delivery associated with traditional Ajax techniques such as polling. However, based on recent progress within WebSockets in the HTML5 specification, Web developers can finally make streaming data to browsers in real-time a reality. Continue reading »
Article looks at how you can design web pages using just CSS and no tables and why CSS is the better and smarter choice for web pages.
Ajax is perhaps the best known RIA technology today. While several implementations of Ajax have arrived, and many software projects involve the use of Ajax; there is still a lack of consistency in the approach and usage of Ajax. There is also a significant confusion regarding which Ajax toolkit should be used, and how? Continue reading »
Anirudh Dewani looks at What is the Google Web Toolkit (GWT)?, the GWT architecture, JRE emulation & IDE support. He also looks at GWT Modules, Optimized JavaScript, Direct Http/JSON – RPC/ Server Side Support. He develops a GWT application highlighting GWT capabilities, including its support for unit testing and internationalization. Continue reading »

Ajax allows us to build Web 2.0 applications with ease. However, it also raises a number of questions. One such very pertinent question is regarding user authentication. User authentication simply means checking the authenticity of the user, How should we ensure that authentication mechanisms are not bypassed, when we use Ajax – in other words, when we deal with asynchronous way of communication, instead of a standard user ID-password based mechanism?