Hi nilupa; IMO this thread has more than one concept. Initially, the version I discussed with you is more of a message monitoring tool, which allow an user to see which message goes through where in the system. It is purely used for debugging services only, and a actually it distributed TCP monitor that helps people debug their distributed application. Features I had in my mind was to
1. Ability to turn on/off message interception 2. When tuned on, it show the system in a UI and let me see all messages went through each link I selected. 3. If messages have a some ID that identify a message sequence, it should let me select a message and find sequence that generated/ lead to that message. Basically, as I mentioned before, it is debugging tool and not a monitoring tool. Then, there is a BAM/System monitoring aspect we heavily discussed in this thread, which is used to monitor a running system. IMHO they are different,yet very useful. However, they are targeted at two audiences and you should not do half of each. Personlly, I am interested in both topics, and willing to mentor/co-mentor either, however, IMO it two projects, not one. Thanks Srinath 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 > > -- ============================ Srinath Perera, Ph.D. WSO2 Inc. http://wso2.com Blog: http://srinathsview.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
