More Related Links
In addition to ASP.NET AJAX, many third-party AJAX libraries are available that
can be used with ASP.NET, although not all of them were specifically designed
within the browser to make manipulation of the browser DOM (Document Object
have their logic running on the server. This means a lot of page refreshes for
potentially small updates to the user’s view. With AJAX, much of the logic
surrounding user interactions can be moved to the client..........
background server calls and retrieve additional data as needed, updating
certain portions of the page without causing full page reloads.............
Among the set of features that the new portlet specifi cation JSR-286 introduces
to make things easier for AJAX implementations, are the options to directly
communicate with the portlet through shared render parameters and resource
Implement AJAX functionality in one of the portlets, using asynchronous server
calls and dynamic HTML.
JBoss portal supports markup through tags on layouts and renderers of the pages.
Special tags are added to layout JSPs that facilitate the placement of AJAX
features on a page. Similarly, renderers are used to interpret the tags and to
render AJAX-driven content. The obvious advantage is the in-built support for
the auto-creation and control of AJAX components on portal pages.
Although AJAX is an exciting technology and provides signifi cant advantages in
terms of performance, usability, and implementation, there are certain
scenarios where using AJAX is not a good fi t. This is especially true when a
lot of custom development is involved in using AJAX libraries.