One of the things I like about tcpmon is that its simple - it doesn't try
to do too much. All its supposed to do, at its core, is just watch tcpip
traffic. So when people want to extend it to do more than that I get
worried. That said - let me tell you what I've told other people - while I
don't like the idea of changing the core tcpmon to do stuff like you've
proposed (mainly because it moves it even more towards a SOAP monitor
instead of a tcpip monitor) - I do, however, like the idea of adding
plug-points where things like what you've developed can be optionally
plugged in. But that's just me.
-Dug
"Eric Y. Kow" <[EMAIL PROTECTED]> on 07/30/2003 10:15:07 AM
To: Doug Davis/Raleigh/[EMAIL PROTECTED]
cc:
Subject: soapmeter (a tcpmonitor spin-off)
Greetings,
I'm writing to ask you some questions about the TcpMonitor which
is distributed with Apache Axis. Namely, are you still involved
in Axis-related development? And would you have any interest
in furthering the development of Soapmeter, a spin-off of your
TcpMonitor code?
Soapmeter helps you to troubleshoot web services and other SOAP-based
applications. It captures the messages exchanged between two SOAP
nodes, and improves your understanding of this activity by creating a
graphical representation of the XML content.
You can find out more at http://soapical.sourceforge.net/soapmeter
Thanks,
--eric
