- Apr 15, 2005
Maybe re SOAP re its legacy; but to definitively state x is y; usually needs to be substantiated by research / survey / ...So you finally concede that for C# and building SOAP services in WCF is the standard? If not please provide one then (I am specifically talking C# and SOAP here). Thanks. (Of course if you're only communicating with other .NET based apps you can add binary transports, but that's not what we're talking about here).
...but hey whatever floats the boat; remember my comments from the onset have not broached the subject of WCF, neither would I re IMO it has arguably as much legacy baggage as SOAP does.
Sure, I tried to cover for both eventualities; but I guess I failed miserably -- point I tried to express is why would anyone who is developing in Java ever choose build web services with C# or even choose to build their backend with WCF -- and of course the same goes for any other language -- hence I'm back to "in Microsoft circles" it could be a de facto or ...there's a good chance it is.I never once said it was the defacto standard for other languages, I merely stated you can call WCF from other languages due the exposure of the WSDL definition.
... but hey at least we can agree SOAP sucks...