Ingo talks about SOAP the way it should be done.
Ok, so let's start to talk about the product: It is about SOAP Services. Actually, they still call it Web Services but in fact, it has nothing to do with the web at all. It is only about SOAP anymore - and it is only about SOAP as a framing format anymore. Frankly, I think that this is a very good thing: using HTTP in your mission critical applications might not be the best idea. Wouldn't it be way cooler if you could just take an XML document, wrap it in a SOAP envelope and send it over whatever reliable protocol you like? While still using all WS-* and GXA specifications?
Cool!
As many are aware, the SOAP specification only defines the message format, and doesn't dictate any protocol bindings.
SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.
It's really cool to see work being done on this (and by someone like Ingo).
Cross-platform, cross-protocol remote procedure calls using well-defined standards. I'll say it again - Cool!