SessionProperties and new producers/temp unavailable producers

[Stefan Hepper <sthepper@hursley.ibm.com>]

Hi,
I think we need to clarify and describe in the spec how the following 
two cases are handled:

1. adding a new producer to an existing shared session
- portlet A1 on prod A and portlet B1 on prod B currently share the 
session property zip with the value 71088
- the user add a new portlet to the page from prod C, portlet C1
- C1 also defines zip as a shared property
- the user expects that C1 would get the zip=71088 from the consumer

2. prod currently not available
- portlets A1, B1, C1 share the session property zip with the current 
value zip=71088
- user sets zip = 43210
- producer C is currently not available when the producer distributes 
the new zip value
- consumer renders the new markup of portlet A1, B1 and a temp not avail 
msg for C1
- in a next render req producer C is available again
- the user would expect that C1 would now get the zip=43210 value and 
render the content for that new zip code

I think if these two use cases are not supported the session paradigm 
will look broken for the end user. It will also be a different behavior 
than in implementations that are session based, like JSR 286.

It seems to me that we need to require that the consumer stores these 
properties in order to support 1. It should not be that when I add 
portlet C1 to my page C1 starts a new session, returns the default value 
for the zip code and the consumer sends this as update to A1 and B1, 
which seems to me the current behavior from my reading of the spec.

Comments?

Stefan