On Wed, Apr 7, 2010 at 2:41 PM, Amila Suriarachchi <[email protected]> wrote: > > > On Mon, Apr 5, 2010 at 5:27 AM, nilupa bandara <[email protected]> wrote: >> >> Hello Everyone, >> >> Let me thank all of you once again for your valuable inputs. >> >> Based on the feedback I've got on initial project idea, I've come up >> with an updated version of the project proposal which is listed >> below[1],[2]. > > Can you please add an diagram which shows the deployment architecture of the > system. This make it more > clear about your work.
I've just updated the proposal with design diagram of the system. Could you please check whether it is reasonable ? Best Regards, Nilupa > > thanks, > Amila. >> >> Best Regards, >> Nilupa >> >> [1] http://wiki.apache.org/general/nilupa/gsoc2010/distributed_tcpmon >> [2] >> http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/nilupa/t127042423893 >> >> >> On Fri, Apr 2, 2010 at 5:01 AM, Samisa Abeysinghe >> <[email protected]> wrote: >> > >> > >> > On Fri, Apr 2, 2010 at 8:23 AM, Samisa Abeysinghe >> > <[email protected]> wrote: >> >> >> >> >> >> On Fri, Apr 2, 2010 at 7:12 AM, Srinath Perera <[email protected]> >> >> wrote: >> >>> >> >>> 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. >> >> >> >> If it is a debugging tool, that is going to be useful. >> > >> > And I think, it would be useful to list out the features it supports. >> > I would also personally prefer some additions to the existing TCPMon >> > where >> > we can add plain text display of secure messages. However, I know that >> > it is >> > complicated, as the middle man is not supposed to change the ttl and the >> > like in WS Security. >> > Samisa... >> >> >> >> Samisa... >> >> >> >>> >> >>> 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 >> >>> <[email protected]> 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 >> >>> > <[email protected]> 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: [email protected] >> >>> > For additional commands, e-mail: [email protected] >> >>> > >> >>> > >> >>> >> >>> >> >>> >> >>> -- >> >>> ============================ >> >>> Srinath Perera, Ph.D. >> >>> WSO2 Inc. http://wso2.com >> >>> Blog: http://srinathsview.blogspot.com/ >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: [email protected] >> >>> For additional commands, e-mail: [email protected] >> >>> >> >> -- >> >> Samisa Abeysinghe >> >> Director, Engineering - WSO2 Inc. >> >> >> >> http://wso2.com/ - "lean . enterprise . middleware" >> > >> > -- >> > Samisa Abeysinghe >> > Director, Engineering - WSO2 Inc. >> > >> > http://wso2.com/ - "lean . enterprise . middleware" >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
