Hi Everyone,

Unless I had cotton in my ears, I think we neared consensus on what a Session is for the purposes of having a sessionID for the interface. Correct me please if I am wrong, but I believe we arrived at a point where we can say that what we mean by Session is the conversation started by one end-user requesting service from one consumer, such that a sessionID is created by the consumer whose responsibility it is to manage this session/conversation with the end-user, providing for delivery of service from one or more producers.

There was also a related concept put forward for consideration called a sharedSession. This concept had many possible configurations, but the basic idea was that something like this was needed, in addition to transientEntities for economical management of multiple portlets within containers, multiple producers within a session, etc.

TransientEntities and sharedSessions were not quite narrowed down enough for consensus to emerge, and I may be mistaken about sessionID, but we certainly worked tenaciously at the interface issues.

Thanks, Rex