Groove, Radio, and Leaky Abstractions
Tim Knip: Groove needs a SOAP-header for security reasons and as Sam Ruby points out, SOAP-headers are around for some years now. Ok, Radio is BDG-compliant - clear - but then soap.rpc.client has to be dropped for interop with Groove.
Rick Olson: I had the same issue trying to get the Muse.Net client to work. It was a little more difficult to use the lower level Radio methods to send headers, but I just wrapped it up in my own wrapper and all was good.
Unquestionably, functions like soap.rpc.client provide value, but abstractions fail. When they do isn't it nice to know that you can drop down to a lower level interface when necessary?