AJAX
It may come as somewhat of a surprise that in a world where the emphasis seemed to have been squarely on writing neat and good server-side code to improve the interaction between website and user, the current revolution starts on the client side. The proliferation of the group of technologies most commonly known as Asynchronous JavaScript and XML, or AJAX for short, has been rapid and its reliance on only open standards has meant that competition for the best use of AJAX has been seen across all web platforms. Its cross-browser, cross-platform nature continues to ensure that.
Whether you use it to implement the more blatantly apparent UI features, such as the instant lookups of Google Suggest, or the subtler features, such as text box watermarking and the invisible updating of selection lists based on the contents selected in others, AJAX is here to stay despite the security risks that it exposes. After the initial commotion in 2005, and the development of several free server-side AJAX libraries such as Anthem.NET and MagicAjax.NET, many asked when Microsoft would come up with its own AJAX implementation.
Tip
If you’re interested in reading about some of the security risks of AJAX, have a look at http://www.cgisecurity.com/ajax/.
In January 2007, Microsoft answered with three distinct downloads for ASP.NET 2.0 and VS2005:
- ASP.NET 2.0 AJAX Extensions 1.0
A library of client-side scripts and a half dozen core controls to place onto an ASP.NET page that render into an appropriate client-side ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access