This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Michele, Securing Web Services, and Composable Web Services
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
So tonight I finally got out of the house for the first time since my surgery on the 15th thanks to Jim Murphy giving me a ride over to see Michele's Bustamente's talk Securing Web Services with WSE 2.0, that I had secured through INETA for our NH group. It was good to see Michele again and her talk, which focused on going past SSL to truly secure Web Services with WS-Security, WS-Policy and such, absolutely rocked! It it a sweet spot for me as we are doing that today with those two specs and moving towards having a WS-Trust exchanging tokens such that edge devices can have a WS-SecureCoversation with servers.
In that regard, I find amusing all the current backlash aggainst the WS-* bunch of specs and the cry not to learn them, bother with them. Maybe some of these people need to spell and define c-o-m-p--o-s-a-b-l-e. Composable means the specs assemble together what you need and only what you need. And if you are going to replace big honking proprietary middleware stacks with SOA loosely-coupled XML standard web services, you sure do need a set of composable services assembled together to replace the things that COM/DCOM/CORBA/RMI/others used to do for you but you can now do in an interoperable manner with standard XML SOAP packets. Phil captures it best in his nice WS-LooseCoupling post with “In other words, it's up to you what you use, and what you don't use. If you don't need any of the WS-* stack, then fine. ..This is why the debate between WS-* and its would-be nemesis REST (ie XML over HTTP without even SOAP let alone any of its WS-* frippery) is a futile distraction. The whole point of SOA is that every participant can set their own rules. In fact, the reason there are so many separate WS-* specifications is that each one is meant to be optional. “
Previous Topic
