OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [wsrp] Coordination reading for the F2F


One of my questions was dropped in this round because it appears it was already raised and settled at the last f2f. As currently formulated, our event types carry no source information (this would be highly unusual in an event system). Just to note that, at a later stage, I will be asking to add a field in the event type that the consumer can place a portletInstanceKey (cf. 6.1.2) into, before delivering an event to an event sink (using the proposed handleEvent rpc). The (currently optional) portletInstanceKey value should be the one the consumer uses for the entity that raised the event. My use case is that event receivers may need to be able to see if two events are from the same portlet window (or even their own consumer side representation, e.g. in a cut and paste).
 
regards,
Andre
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 25 February 2004 18:54
To: wsrp@lists.oasis-open.org
Subject: [wsrp] Coordination reading for the F2F


Attached is a version of the semantic document the SC has been using to work our way through the evolving coordination model and attendant questions. The questions at the end of the document are roughly in the order we intend to address them at the F2F.



Rich


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]