I'm starting to document the Pluto integration work on the wiki http://www.ja-sig.org/wiki/display/UPC/Pluto+1.1+Integration
At this point there are notes about features that will needed to be added to interfaces that extend IChannel, some terminology definitions to help clarify how Pluto and uPortal match up, and points of integration. One of my questions is here regards the portlet object model that was designed for the sandbox portal code. One big difference between it and how (I believe) channels work is when you subscribe to a portlet there are two objects created, an entity and a window. The subscription is to the entity, this is where data like runtime portlet preferences is stored. The window is what is viewed, it tracks the current WindowState, PortletMode and request parameters. The big advantage to this model is it would be feasible to have multiple windows for one entity, such that the detached functionality could result in a temporary window for the entity and the portlet could be interacted with both in the layout and in its own window independently. What I'm really looking for from that description is some input from the people on this list that are more familiar with the IChannel & uPortal rendering functions than I am. Please feel free to ask questions, poke holes, ramble on about any of this. The more feedback I can get throughout this work the better the end result will end up being. -Eric
smime.p7s
Description: S/MIME Cryptographic Signature
