IPC
Get flash to fully experience Pearltrees
Client-side Inter-Portlet Communication - Wiki - Liferay.com
Liferay JavaScript Event System # The client-side mechanism to communicate portlets is based on events. Using events instead of direct js calls accross portlets is very important since it's not possible to know at deployment time which other portlets will be available in a give page. By firing/triggering an event one portlet just notifies that something has happened, and then one or more of the other portlets in the page might be listening and act accordingly. So, what Liferay.bind does is that it lets you listen in for any arbitrary event (it could be anything the developer decides, or an existing one, though we don't have many just yet).
Eventing and Shared Render Parameters - Wiki - Liferay.com
Shared render parameters: allows portlets to set params that can be read by other portlets. This rather simple mechanism will probably be enough for all but the most complex communication needs Events: needed for complex scenarios. The main advantage of this second method is that it allows a fully decoupled communication. A portlet issues an event and doesn't have to care if there is anyone listening for it.
TWiki . Portlet . JSR168FAQ
As the new Java.net infrastructure contains project-level wikis, this main wiki will be shut down in the near future. For wiki page export and general wiki questions please contact the site admin at communitymanager@java.net . A portal can be best described as a web site that acts as a "point of entry" or a gate to a larger system. While it seems pretty difficult to define a portal in the strictest sense, these are some of the common features of portals: A portal server however provides a base infrastructure for rapidly developing/deploying portals. It also provides, out of the box implementations of most of the services that any portal would require.