Re: [wsrp] navigational state change

[Wesley Budziwojski <Wesley.Budziwojski@Sun.COM>]

Subbu,

On one hand just nomenclature but on second thought I would agree with 
you that direct (P->C) vs indirect (P->EU->C) is perhaps the most 
accurate  saying.

On other hand was trying to explore related use case that since the 
navig state changes "indirectly" by skipping pBI  it might lead to some 
form of discrepancies. It seems that Mike nailed it down.

Thanks,
Wesley


Subbu Allamaraju wrote:

> "The Consumer SHOULD supply this value as the navigationalState on the 
> subsequent invocations for this use of the Portlet for at least the 
> duration of the End-User's interactions with this aggregated page in 
> order to maintain End-User state. The Consumer is not required to 
> persist the navigationalState for longer than this set of 
> interactions, but can provide such a persistence if desired."
>
> On your question on direct vs indirect, I don't understand why a 
> portlet can't encode new navState in a URL during a getMarkup?
>
> Subbu
>
> Wesley Budziwojski wrote:
>
>> Subbu,
>>
>> "In that sense, the portlet is not changing its state directly."
>>
>> One would think that direct or indirect change is a change :)
>> Interesting; Direct change - meaning Consumer changed navig state and 
>> sent it in markupParam) or
>> indirect change -only Producer is aware of the change (new state) and 
>> renders based on that?
>>
>> What does following render() and reload expected to do?
>>
>> Thanks,
>> Wesley
>>
>>
>> Subbu Allamaraju wrote:
>>
>>> In this case, the portlet is not returning new navState, but is 
>>> encoding  this state in a URL. This is navState change, but happens 
>>> when a UA submits the request to the consumer. In that sense, the 
>>> portlet is not changing its state directly.
>>>
>>> Also not that this example is true only for render URLs.
>>>
>>> SubbuThe Consumer SHOULD supply this value as the navigationalState 
>>> on the subsequent invocations for this use of the Portlet for at 
>>> least the duration of the End-User's interactions with this 
>>> aggregated page in order to maintain End-User state. The Consumer is 
>>> not required to persist the navigationalState for longer than this 
>>> set of interactions, but can provide such a persistence if desired.
>>>
>>> Wesley Budziwojski wrote:
>>>
>>>> Section 3.12
>>>>
>>>> "Examples of when one of the optional steps 
>>>> (performBlockingInteraction and handleEvents) might not be used 
>>>> include:
>>>>
>>>>    * The End-User interacting with a URL that simply looks to render
>>>>      the Portlet's markup with a different navigational state (e.g.
>>>>      with the next set of results from a search). In this case, 
>>>> both of
>>>>      the first two steps could be skipped. "
>>>>
>>>> It seems that  to render Portlet's mark-up with a different 
>>>> navigational state implies that  Portlet needs to change its 
>>>> navigational state and
>>>> if so the change of the Portlet's state should happen in PBI or 
>>>> there is no navigational state change in this use case?
>>>>
>>>> Thanks,
>>>> Wesley
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe from this mail list, you must leave the OASIS TC that
>>>> generates this mail.  You may a link to this group and all your TCs 
>>>> in OASIS
>>>> at:
>>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this mail list, you must leave the OASIS TC that
>>> generates this mail.  You may a link to this group and all your TCs 
>>> in OASIS
>>> at:
>>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>>
>>
>>
>