[RESOLVED] WCF - Web Service

[Negative0]

I have a WCF web service that I wrote that talks to a backend API. It works great for a lot of our projects, but we are now looking at exposing this API to some of our customers. Our customers use a wide variety of web technologies including Java and Cold Fusion.

What I am looking for is, what is a good approach to give them access to the WCF services that will make them usable? Do we write a non-WCF wrapper around the web service, to make it easier for them to call? From looking at the WSDL generated by the WCF web service, it can be rather difficult to follow.

[mendhak]

You don't have to. Each of your clients should have their own platform specific APIs that let them talk to SOAP web services. A quick search tells me that Java already has SOAP libraries. I know that PHP has SOAP libraries. CF - since there are articles on it, must be a way.

If you want to make it easiest for them, then expose the service as a basicHttpBinding so that it's a SOAP 1.1 service. wsHttpBinding would be SOAP 1.2 and you don't know for sure whether all of your clients can deal with it.

[Lightning]

I agree with mendhak, the basichttp binding works with any technology that can make a http request, even VB6

[Negative0]

OK thanks guys, you gave me a push in the right direction. I think I am understanding the bindings much better now after doing a bit of reading.