- This topic has 1 reply, 2 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
It is incredibly cumbersome to work wtih TCP Monitor the way it’s implemented now.
1. Move TCP monitor activation out of preferences. Seeing my configurations there is handy but starting, stopping, and everything else is simply not fluid.
2. Monitors — I’d like to have an XPath expression for HTTP/XML type conversations (yes, I know there’s a performance hit; big latency for one) or a regular expression (on HTTP headers and body content) that could then enable or disable a breakpoint.
3. Logging of all data (in, out, headers, response codes) to a file. Let me extract out the data easily. It’d be really cool if I could then use this file (and of course with some wrapper class) with BIRT and TPTP to drill down on traffic and correlate it all with debug logs and performance data.
