This is true if it is a debugging tool and fires all messages to the 'central' place.
However, still, the 'firewall' aspect needs to be taken into account. For example, the current dual channel is quite useless when not in same network and there are firewalls. So async dual channel might not work in a real setup debug. Samisa... On Fri, Apr 2, 2010 at 12:17 AM, Andreas Veithen <andreas.veit...@gmail.com>wrote: > Probably the right answer to this question is: none. Why would the > individual nodes intercepting the messages use publish/subscribe? They > should all send them to a central place (or back to the sender of the > original request). > > Andreas > > On Wed, Mar 31, 2010 at 16:51, Samisa Abeysinghe > <samisa.abeysin...@gmail.com> wrote: > >> Then we can take this to next level by adding this module to all > >> services in a system , configuring modules to send all collected > >> messages to a pub/sub channel, and subscribing to those messages via a > >> UI, and depicting those messages through a UI. > > > > What pub/sub model do you plan to use? WS-Eventing? > > > > Samisa... > > -- > > blog: http://samisa-abeysinghe.blogspot.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://wso2.com/ - "lean . enterprise . middleware"
