John Burkhardt on the SOAP-header issue I stumbled on trying to let Radio use Groove Web Services. Simon Fell describes the problem in some more detail. Dave Winer argues that Radio's SOAP-stack is BDG-compliant, and new applications should be backward compatible.  Which in this case would mean: SOAP-Headers are not in the BDG so Groove should adapt and drop the headers? Hmm, I'm not very interested in questions like this, I just want something that works. All I'm saying is:  I can't add a SOAP header when using Radio's builtin SOAP-client: soap.rpc.client. Radio's soap.rpc.client function can only add the SOAP-Body apparently. 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. So...I understand Dave Winer's point that new apps should be compatible with older apps, but Groove also scores points when wanting to move foreward using the specs of today. Bottomline: too bad I can't use Radio's SOAP-client!

Which on the other hand is rather fun , because now I got the chance to write a sort-of Radio SOAP-client which can send the disputed header. Whether this is real interop is a theoretical question, but i'm pretty sure it works. 200 OK?!