Re: Re[2]: [wsrp-dev] What is interaction state?

[Rich Thompson <richt2@us.ibm.com>]

Since this is specific to the interaction with the portlet, a reasonable 
approach for Producer support is to provide a means by which the portlet 
can indicate the items to encode as interactionState and then on 
activation make these items available to the portlet again in a manner 
consistent with the overall interfaces between the Portlet and Producer. I 
would note that there is a significant overlap with navigationalState ... 
the key difference is that interactionState is scoped to the 
performBlockingInteraction invocation. These same considerations also 
apply to the resourceState field, introduced in v2, which is scoped to a 
getResource invocation.

Rich Thompson
OASIS WSRP TC Chair
IBM T.J. Watson Research Center / Hawthorne, NY



From:
Roman Pedchenko <roman.pedchenko@exoplatform.com.ua>
To:
Rich Thompson/Watson/IBM@IBMUS
Cc:
"Alexey Zavizionov" <alexey.zavizionov@gmail.com>, 
<wsrp-dev@lists.oasis-open.org>
Date:
12/05/2007 09:37 AM
Subject:
Re[2]: [wsrp-dev] What is interaction state?



Hello Rich,

Wednesday, December 5, 2007, 2:27:35 PM, you wrote:

> Suppose a particular interaction needs a parameter which is known
> when the markup is being generated (i.e. not one supplied by the
> user). If the interaction is sourced off a form, such items are
> often placed in hidden fields such that they get sent when the
> action is activated. In many ways, interactionState provides the
> equivalent functionality for any of the other ways in which the
> action could be activated (button, hyperlink, etc) by encoding the 
information into this field.

But what criteria does a Producer have to use to detect what
exactly parameters it must transmit as interactionalState?

-- 
Best regards,
 Roman                 mailto:roman.pedchenko@exoplatform.com.ua