Yossi,
The sessionID somehow implies that the producer is keeping all state
key-ed off with the sessionID.
The markupParams allows (actually it just makes it easy) to keep state
(for the portlet entity) outside of the producer. Of course you could
serialize all the markupParams in a blob an use that as sessionID.
I also see this separation as superficial, but I think it will make
things easier and manageable for vendors that want to have stateless
producers.
Regards.
Alejandro
Tamari, Yossi wrote:
> ...
> I still think that separating sessionID from markupParams is
> superficial, since consumers really need to treat them in
> the same way.
>
