May
30th,
2004
As everybody knows, WSE 2.0 was released last week. One thing I find myself wishing for was to be able to use Simon's excellent TcpTrace with the TCP Transport in WSE. Alas, WSE doesn't like it when the reply endpoint is on a different port than the request (it's possibly comparing the two endpoint URLs, atlhough I haven't dug into it) :(
Update: A few hours after posting this, my good friend Christian Weyer sent me an email mentioning that this indeed can be made to work, by simply taking advantage of the routing facilities and inserting a Via element in the endpoint reference that points to the port TcpTrace is listening on from the client side! Way cool! Thanks Christian! :)