Tool Name: IPC Developer(s): Rahim Lakhoo
|Description of Tool||Inter-Portlet Communication|
|Origin of Tool||ACET, AMG University of Reading|
|Agreement with original Authors (please state process and nature of agreement)||TBC|
|Platform used (please tick)||JetSpeed2: uPortal: GridSphere: x Liferay: eXo: CHEF (OGCE): Sakai: x StringBeans: Other:|
|Integration Technology used (please tick)||JSR-168: x WSRP: OKI OSID Service API: Other:|
|In repository? (note discussions with NeSC and status|
|With OMII? (note discussions with OMII and status||
|Integration signed off by||Mark Baker|
Description of work undertaken during porting:
The aim of this work is to provide a means for portlets to communicate and share information, by using standard JSR-168 components.
Sakai VRE reports available from http://acet.rdg.ac.uk/projects/vre/docs.php. System documentation and details are available from http://acet.rdg.ac.uk/projects/vre/ipcportlet.php.
Ongoing support issues:
Tool use case:
Currently the JSR-168 specification does not define a way for portlets or portlet applications to communicate with each other. This library provides an Asynchronous Registry Session Centre (ARSC), through which different portlet applications can communicate information and objects.
Help information for tool users:
Technical reports, presentations, installation guides and manuals are