Guidelines are a good idea. In general, I
would suggest that any bulk operation results from a logical need to batch, for
example, for copyPortlets(), an admin may select/highlight several portlets and
then request they be copied to another registration. In other worlds, we should
not batch just to optimize use of lower level transports. And we should always note
that batching may not imply any atomicity, though both efficiency and fault tolerance
can be aided by our logically batched operations.
Regards,
Andre
From: Rich Thompson
[mailto:]
Sent: 04 March 2005 19:16
To:
Subject: RE: [wsrp] Issue #31:
handleEvent or handleEvents?
This issue has been discussed under an email subject
line of " [wsrp] handleEvent or handleEvents?". Before tailing off,
this thread came to several guidelines for any solution moving this operation
back to a bulk character:
1.
Portlets are loosely coupled components integrated onto the page by the
Consumer.
2. Events are independent notifications that something has occurred, which
receiving portlets may use to impact their state.
3. There are times when a Consumer will care what
failures have occurred (e.g. for retry purposes).
4.
Portlets should be able to indicate they also care about event processing
failures.
Any
additional comments before we move to drafting a solution?
Rich
