kawaijenbromo wrote: > What about the following approach, based on WS-Notification: > You implement a central broker based on the WS-NotificationBroker > pattern, which is your PubSub hub. > > *Pros:* > > * It is fully WS-based for all actors of the game. "Everybody" is > supposedly able to deal with the hub thru SOAP and WS-Addressing > > * The spec is quite mature; it provides the broker pattern almost > mandatory for EDA > > - deals with Push and Pull notification model > - even allows on-demand publishing > - has a Topic-based and a content-based subscription models > > * Implementations: you have a WebSphere 6.1 and an Apache ServiceMix one > > > *Cons:* > > * Probably the implementations are not very stable (sort of 1.0 > releases) > * It is not a real standard due to the standard battle with > WS-eventing which will not converge before years > > *Issue* > Is it possible to interact with the above PubSub hub only with a SOAP + > WS-Addressing capable client? First analysis is that only the hub needs > to be WS-Notification compliant. Its users are mere SOAP clients. So any > Java or .NET recent WS toolkit will do. > > But we have not verified that the above assumption is actally true ... > Work in progress
Can you elaborate on what you think is the biggest reason why there is not convergence and/or few faithful, debugged implementations? I have my own thoughts that revolve around the details of all these pieces. But, I'm curious what you've experienced, seen and heard. Gregg Wonderly
