http://blogs.seapine.com/grant/net-web-service-moving-faster-than-light.html Tue, 06 Jan 2009 13:37:37 +0000 http://wordpress.org/?v=2.5.1 http://blogs.seapine.com/grant/net-web-service-moving-faster-than-light.html#comment-1684 Crouching tiger, coding monkey » Grant.JinxedSelf() == true Tue, 06 Nov 2007 17:53:18 +0000 http://blogs.seapine.com/grant/net-web-service-moving-faster-than-light.html#comment-1684 [...] even ten hours after I complimented ASP.Net it has already come back to haunt [...] [...] even ten hours after I complimented ASP.Net it has already come back to haunt [...]

]]> http://blogs.seapine.com/grant/net-web-service-moving-faster-than-light.html#comment-678 Sean Fri, 13 Apr 2007 15:08:56 +0000 http://blogs.seapine.com/grant/net-web-service-moving-faster-than-light.html#comment-678 Now you'll have to update your toolbox. The first thing that happens when you start to do web services is that everyone will blame you when something doesn't work. Naturally, you'll want to blame them for an incorrect request. Something like Wireshark (nee Ethereal) is invaluable in this area. Setting the capture filter to the port your services are running on and the display filter to syns or acks will usually let you find the right request the quickest. While that one can handle https, it's a bear. Covelight ClearWatch (not ClearHTTP, at least I don't think) makes watching https downright easy at least for Windows boxes. Or you can use one of them fancy SOAP Management proxies that will capture every request and response. Then comes the whole thing around the services themselves. I vote for SOAP only if necessary, WSDL first, make sure it's encapsulated, atomic and reusable. Well, that's what I have for now. Good luck! Now you’ll have to update your toolbox. The first thing that happens when you start to do web services is that everyone will blame you when something doesn’t work. Naturally, you’ll want to blame them for an incorrect request. Something like Wireshark (nee Ethereal) is invaluable in this area. Setting the capture filter to the port your services are running on and the display filter to syns or acks will usually let you find the right request the quickest. While that one can handle https, it’s a bear. Covelight ClearWatch (not ClearHTTP, at least I don’t think) makes watching https downright easy at least for Windows boxes. Or you can use one of them fancy SOAP Management proxies that will capture every request and response.
Then comes the whole thing around the services themselves. I vote for SOAP only if necessary, WSDL first, make sure it’s encapsulated, atomic and reusable.
Well, that’s what I have for now. Good luck!

]]>