- From: Ugo Corda <UCorda@SeeBeyond.com>
- Date: Mon, 14 Jun 2004 09:48:19 -0700
- To: "Amelia A Lewis" <alewis@tibco.com>
- Cc: <www-ws-desc@w3.org>, <hugo@w3.org>, <xml-dist-app@w3.org>
> > > In a pub/sub world, an out-only pattern (or any out-initial > > > pattern) is a nice fit, and we expect to see these widely > > > used. This is because, in pub/sub, the service is talking, > > > not listening; publishing, not serving. > > > The other nodes interacting with the service are not > > > requesters/clients, but listeners/subscribers. > > > > > > > That's exactly my point. In that kind of scenario, it should more > > important to focus on the endpoint of the > listener/subscriber than on > > the endpoint of the service itself. > > No, no, no! Absolutely not! The *publisher* defines what it > publishes. > It publishes en masse. It is not controlled by the > subscriber. It just spews. It's up to the subscriber to > separate wheat from chaff. > If you are in a situation of brokered notification, the server only talks directly to the broker, and the only endpoint of relevance is the endpoint of the broker node. Ugo
Received on Monday, 14 June 2004 12:48:50 UTC