MHonArc v2.5.2 -->

















wsia message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: RE: [wsrp][wsia][wsrp-wsia joint itnerfaces] Actions




From: Eilon Reshef <eilon.reshef@webcollage.com>
To: 'Michael Freedman' <Michael.Freedman@oracle.com>,'wsia' <wsia@lists.oasis-open.org>, 'WSRP' <wsrp@lists.oasis-open.org>
Date: Tue, 11 Jun 2002 20:59:41 -0400






Title: Message



My understanding is that actions are a way to support multi-page 
portlets. E.g., a search portlet has two buttons "prev" and "next", each one is 
a separate action. The portlet receives this action and generates a new page 
accordingly. It can generate it as part of the action invocation or in a later 
phase (getFragment).

  

  
-----Original Message-----
From: Michael Freedman 
  [mailto:Michael.Freedman@oracle.com]
Sent: Tuesday, June 11, 2002 
  8:34 PM
To: wsia; WSRP
Subject: [wsrp][wsia][wsrp-wsia 
  joint itnerfaces] Actions


  
I would like to open another discussion parallel to our 
  session debate.
From the perspective of the protocol 
  defined in the latest draft I can't
figure out the 
  semantic difference between performAction and
getFragment.  Each seem to be capable of returning the same 
  stuff.  Why
do we need both?  I.e. how are 
  they semantically different?
     
  -Mike- 


  
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the 
  subscription
manager: <http://lists.oasis-open.org/ob/adm.pl> 
  







References:

[wsrp][wsia][wsrp-wsia joint itnerfaces] Actions
From: Michael Freedman <Michael.Freedman@oracle.com>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]


  









Powered by eList eXpress LLC