Skip to main content
Software Engineering

Return to Answer

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link
Community Bot
Community Bot
  • 1

The only interoperable endpoint supported by WCF are the http ones (ie SOAP) and of those, I would steer well clear of the wshttpbinding option as it doesn't really interoperate with non-Microsoft SOAP clients. (there are other SO questions about this, just trust me. basicHttpBinding is the one you want).

From that point, you're basically making SOAP 1.1 calls into a webservice. You can configure your WCF service to listen on 2 endpoints, one for internal clients, the other for external ones. Use one of the security options on the endpoint (probably TransportCredentialsOnly option as iOS will not support all the Windows-only security options such as NTLM that you can use). Making web service calls should be trivial with iOS.

(ah, quick google shows that there is now a webHttpBindingwebHttpBinding option that exposes your service as a REST-based http server. this is a much better choice than bloated and poorly defined SOAP. I'd use this now).

The only interoperable endpoint supported by WCF are the http ones (ie SOAP) and of those, I would steer well clear of the wshttpbinding option as it doesn't really interoperate with non-Microsoft SOAP clients. (there are other SO questions about this, just trust me. basicHttpBinding is the one you want).

From that point, you're basically making SOAP 1.1 calls into a webservice. You can configure your WCF service to listen on 2 endpoints, one for internal clients, the other for external ones. Use one of the security options on the endpoint (probably TransportCredentialsOnly option as iOS will not support all the Windows-only security options such as NTLM that you can use). Making web service calls should be trivial with iOS.

(ah, quick google shows that there is now a webHttpBinding option that exposes your service as a REST-based http server. this is a much better choice than bloated and poorly defined SOAP. I'd use this now).

The only interoperable endpoint supported by WCF are the http ones (ie SOAP) and of those, I would steer well clear of the wshttpbinding option as it doesn't really interoperate with non-Microsoft SOAP clients. (there are other SO questions about this, just trust me. basicHttpBinding is the one you want).

From that point, you're basically making SOAP 1.1 calls into a webservice. You can configure your WCF service to listen on 2 endpoints, one for internal clients, the other for external ones. Use one of the security options on the endpoint (probably TransportCredentialsOnly option as iOS will not support all the Windows-only security options such as NTLM that you can use). Making web service calls should be trivial with iOS.

(ah, quick google shows that there is now a webHttpBinding option that exposes your service as a REST-based http server. this is a much better choice than bloated and poorly defined SOAP. I'd use this now).

Source Link
gbjbaanb
gbjbaanb
  • 48.7k
  • 7
  • 105
  • 173

The only interoperable endpoint supported by WCF are the http ones (ie SOAP) and of those, I would steer well clear of the wshttpbinding option as it doesn't really interoperate with non-Microsoft SOAP clients. (there are other SO questions about this, just trust me. basicHttpBinding is the one you want).

From that point, you're basically making SOAP 1.1 calls into a webservice. You can configure your WCF service to listen on 2 endpoints, one for internal clients, the other for external ones. Use one of the security options on the endpoint (probably TransportCredentialsOnly option as iOS will not support all the Windows-only security options such as NTLM that you can use). Making web service calls should be trivial with iOS.

(ah, quick google shows that there is now a webHttpBinding option that exposes your service as a REST-based http server. this is a much better choice than bloated and poorly defined SOAP. I'd use this now).