Re: [wsrp] navigational state type

[Richard Jacob <richard.jacob@de.ibm.com>]

well agree,

the transient scope is kind of not well defined since it's the Consumer's
choice to really define the what the lifetime of the scope is.
There is no tie to portlet sessions on the producers or cookies.
I think the only thing the scope expresses is the expectation of a portlet
that properties stored in that scope endur some sort of life time. In this
case we say "well this is the lifetime of whatever the Consumer thinks is
appropriate as a end user session".
The navigational scope (Public NavState) is yet another scope which can be
used by the portlets with the expectation that properties in this scope
will survive end user sessions and are probably persistet (bookmarks).

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com


                                                                           
             Wesley                                                        
             Budziwojski                                                   
             <Wesley.Budziwojs                                          To 
             ki@Sun.COM>               OASIS WSRP TC                       
             Sent by:                  <wsrp@lists.oasis-open.org>         
             Wesley.Budziwojsk                                          cc 
             i@Sun.COM                                                     
                                                                   Subject 
                                       [wsrp] navigational state type      
             04/27/06 02:18 AM                                             
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




I meant to ask this question some  time ago.

I was wondering what were the main attribute(s) of  "navigational state"
to calling it out as a different  from "transient" and "enduring"
(or persistent as it was in  WSRP 1.0) statefull type besides the
purpose of guaranteeing the correct rerendering multiple times?
It seems that it might have been classified as transient state even it
can be optionally persisted by consumer or browser.
 From life cycle perspective it seems to be started as an explicit
operation is transient(?)  and no explicit operation is required to
destroy it?
Well it is not perfect fit but then new life cycle might be worth it
defining in section 3.4 then?
Would it be any reasonable notion of "navigational scope" that is worth
mentioning and contrast in 3.5?

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