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] spec-2.0-draft-05: events and blocking actions

> There hasn't been an agreement on blocking semantics yet. I would be 
> against any semantics beyond requiring all event distribution (Note that 
> a Consumer could consider a Portlet which hasn't responded in a timely 
> manner to have finished, but failed to return a response) to end before 
> starting the getMarkup step.

I agree that the consumer should wait for event distribution to complete 
before starting getMarkup step. I've a follow-up question on the nature 
of event distribution.

Can a consumer dispatch events concurrently to various producers?

If the answer "yes" or "may be", then another question to ask is whether 
a consumer can dispatch two events (or two batches of events) to a 
producer for the same portlet? If the answer is "yes", then it is going 
to complicate state management for the consumer. This would also make 
the outcome less predictable. It would be hard to debug for 
portal/portlet developers.



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