Comments on SessionParams and SessionContext

[Subbu Allamaraju <subbu@bea.com>]

Regarding the questions raised by Mike on the current wording of these 
structures, I have the following comments:

-------------------------------------------------

SessionContext.changedSessionProperties

These properties are not necessarily "changed". They may also be 
properties that just came into being (pre-specified in 
PortletDescription, of course). How about calling it "sessionProperties"?

-------------------------------------------------

SessionParams.sessionPropertyUpdates

The same comment applies for this field too. It would be simpler to just 
call these sessionProperties that the portlet may be interested in.

On the question of the name of the SessionContext structure, I would not 
want to change the name of a well-known structure, particularly since 
most implementations will not be exposing such a name to 
portlet/application developers.

-------------------------------------------------

Description of sessionParams (Sec 6.1.2):

The current description reads like

"... and coordination-oriented updates so that the portlet will be able 
to reference this state and therefore process the request in a manner 
meeting the End-User's expectations"

The reference to "therefore process the request..." does not seem be 
adding any value to the semantics of sessionParams. As far as the 
protocol is concerned, this is state that the portlet expressed interest 
in. I would suggest the following:

sessionParams; The consumer uses this field to supply the Producer's 
reference to a portlet session and any new/changed session properties. 
The supplied session properties may have been supplied by other portlets 
or by the consumer itself. The Portlet MUST declare the properties it 
would like to receive in the sessionPropertyDescriptions field of its 
PortletDescription.

Subbu