Glenn, I have a question I hope you can help clear up for me. It appears that the StateManager is quite similar to a possible PortletSession. How would this StateManager differ from a PortletSession?
Wouldn't the state of a Porltet be something like its condition, like minimized, maximized, etc? The proposal seems to allow for a lot of data pertaining to the Portlet outside of its State to be stored. What if each Portlet consisted of an independent Session for each Portlet Instance and User. This would allow for any transient information to be stored per Portlet Instance per User. A wrapper on the session object to encode all attributes with name space information could achieve this goal. To encode with Portlet Instance - PortletNamespaceMapper.encode(portletInsanceId(or peid), attributeName) - any ids you want to use for encoding could be added in addition to the portlet instance id. We are currently utilizing the PortletSession (from portlet_api branch) with the current cvs version of Jetspeed to achieve much of what you are proposing. I believe the name of PortletSession would be less confusing than "State" and that the PortletSession could be extended to meet the additional needs in the proposal. Maybe I am completely off on what you are proposing as a "State" of a Portlet. If so please explain. thanks, Marcus -----Original Message----- From: Glenn Golden [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 11, 2002 6:28 AM To: Jetspeed-Dev ([EMAIL PROTECTED]) Subject: State Manager Proposal I have submitted a proposal for a State Manager capability for Jetspeed. This can be found in: proposals\StateManager.txt For your convinence, a copy is attached. I look forward to your comments. - Glenn -------------------------------------------- Glenn R. Golden, Systems Research Programmer University of Michigan School of Information [EMAIL PROTECTED] 734-615-1419 http://www-personal.si.umich.edu/~ggolden/ -------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
