wsrp-coord message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [wsrp-coord] Teleconference on July 9th at 11:00 ET
- From: Rich Thompson <richt2@us.ibm.com>
- To: wsrp-coord@lists.oasis-open.org
- Date: Wed, 9 Jul 2003 09:07:15 -0400
I am able to start an hour later, anyone
not able to meet at 12 ET? Thanks for the offer to set up a WebEx conference,
our Sametime capacity is still fully booked.
Rich Thompson
| "Tamari, Yossi" <yossi.tamari@sap.com>
07/09/2003 05:30 AM
|
To:
"'wsrp-coord@lists.oasis-open.org'"
<wsrp-coord@lists.oasis-open.org>
cc:
Subject:
RE: [wsrp-coord] Teleconference on July
9th at 11:00 ET |
Hi,
Even though I would really like
to attend today's teleconference, I will not be able to, because of another,
pre-scheduled, important meeting.
Is it maybe possible to delay
the teleconference by one hour? If so, I can arrange a WebEx meeting if
Rich is unable to arrange a SameTime meeting.
In case I don't attend, here are
my first thoughts on the ideas in the presentation:
* I am not sure I can see value
for post getMarkup step. any use cases?
* Events loop prevention can probably
be done by the consumer, without effecting the data structure. We need
to define what is the "minimum requirements" from such a loop
prevention algorithm.
* I would like us to discuss again
the need for enhancing the property model and adding events on property
changes. (Who are the intended clients of these events? the consumer? other
portlets? why not let the producer who changes a property decide if it
wants to send its own event when this happens?)
* I don't see a real reason for
the consumer to manage its subscriptions to portlet events. It seems to
me that the events can be sent always from the producer and the consumer
can ignore them. I think in general more bandwidth will be required by
subscribe/unsubscribe messages than by the events themselves. This feature
would also require the producers to manage subscription lists, which I
would like to avoid. We can add this as an optimization that neither producer
or consumer must implement.
* On the other hand, this proposal
requires that portlets statically define which events they subscribe to,
while I see value for doing this dynamically (more return parameters for
PerformBlockingInteractionResponse and handleEvents).
* In general, I like the main
model proposed here (with handleEvents, etc), and don't think we should
support (at least for V2) any of the other models (where the producer must
initiate SOAP calls), including the grid model (which as far as I understand
is also a P2P model).
Yossi.
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Tuesday, July 08, 2003 8:43 PM
To: wsrp-coord@lists.oasis-open.org
Subject: [wsrp-coord] Teleconference on July 9th at 11:00 ET
Importance: Low
The details for this conference call are located at http://www.oasis-open.org/apps/org/workgroup/wsrp/wsrp-coord/event.php?event_id=1669&
which now includes an agenda.
I have uploaded the framework update proposal which the SC asked me to
work on back in February. The event details reference this presentation.
I have been unable to schedule a meeting like we have used at F2F meetings
for walking through this, but will keep trying.
For reference sake, the callin information is:
USA Toll Free Number: 866-769-7222
USA Toll Number: +1-203-566-0687
PASSCODE: 377048
Rich
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]