Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Share this Page URL
Help

Chapter 12. Ajaxing portlets > Cross-domain Ajax - Pg. 488

488 WARNING C HAPTER 12 Ajaxing portlets Because the Book Catalog portlet doesn't use server-specific exten- sions (like CometProcessor or Continuations ) to scale when server load increases, the Book Catalog portlet doesn't represent a scalable Comet appli- cation. If you're using Jetty 6, DWR transparently uses Jetty's Continuations to handle Reverse Ajax, making the Book Catalog portlet scale well when the load on the server increases. 12.9.4 DWR integration with other frameworks DWR can easily be used along with frameworks like Spring, Hibernate, and JSF . For instance, you can use a DWR creator, which uses a Spring bean or a JSF bean. You can also return a Hibernate object using HibernateBeanConverter . You should refer to the DWR website to learn more about the various integration options available for the framework you're using (http:/ /directwebremoting.org/). Let's now take a brief look at cross-domain Ajax and the issues involved. 12.10 Cross-domain Ajax Cross-domain Ajax refers to a scenario in which an Ajax request is sent from a web page or portal page, downloaded from domain X, to a server that is in domain Y. Let's say your web portal's domain name is www.my-bookportal.com (domain X), and one of the portlets in your web portal needs to asynchronously access a servlet