W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > October 2009

[Bug 7970] Eventing: clarify role of event source

From: <bugzilla@wiggum.w3.org>
Date: Thu, 29 Oct 2009 21:33:25 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1N3ccX-0003PV-3Z@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7970





--- Comment #2 from Wu Chou <wuchou@avaya.com>  2009-10-29 21:33:24 ---
Created an attachment (id=777)
 --> (http://www.w3.org/Bugs/Public/attachment.cgi?id=777)
A proposal to issue 7970

A proposal to issue 7970 that can support the existing as well as the
clustering deployment model.

Use case: In some data center or high volume event processor, events may be
delivered from a special event dispatcher or from a pool of high speed event
dispatchers, not necessarily from the event source endpoint. 

Rationale and benefits: 1) Event dispatcher pools can be shared by all event
sources to improve the event dispatch throughput. 2) These event dispatchers
can be on high speed links (IP addresses) as part of the infrastructure. 3)
There is no need to implement a http client event dispatch for every single
event source. For example, there might be 10,000 individual event sources on
the platform, but only 10 high speed event dispatchers. 4) For some resource
limited devices, the resource hungry event dispatcher may reside in a separate
but more resourceful environment from the event source.

The attached proposal supports this clustering deployment model . In addition,
by making the event dispatcher explicit, it supports the pull-model in event
delivery and IP-blocking as in current model. 


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 29 October 2009 21:33:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 29 October 2009 21:33:28 GMT