What are the limitations of the BasicHttpBinding?

Question

I should develop a client application (for Windows Phone 7) that is able to send requests to a web service created using WCF. The applications that run on Windows Phone 7 can only send HTTP calls, therefore they can use only BasicHttpBinding as regards WCF. For this reason, I have to use BasicHttpBinding in the client application.

Which types of web services can communicate with a client that supports only BasicHttpBinding? Should these web services also be developed using the same binding?

Has a web service created using BasicHttpBinding some limits on the frequency of the received messages? Has a client created using BasicHttpBinding some limits on the frequency of the sent messages? If so, why? If so, could this limit be changed? If so, is this limit related to received messages from the same client?

@JohnSaunders: Do `WSHttpBinding` web services support `BasicHttpBinding` clients? — enzom83, Mar 04 '12 at 15:34
No, of course not. You didn't say the limitation was `basicHttpBinding`, you said the limitation was http. — John Saunders, Mar 04 '12 at 15:36

score 2 · Accepted Answer · edited May 23 '17 at 10:24

2

Anything that supports SOAP 1.1 should be able to call a service using BasicHttpBinding.

As far as limits go, the only limits for a service is how quickly your application can process the incoming messages. There is a default limit of 64KB size per message, but you can adjust that by changing the MaxReceivedMessageSize setting.

You may want to look at this question for more information on BasicHttpBinding vs WsHttpBinding: basicHttpBinding vs wsHttpBinding

edited May 23 '17 at 10:24

Community

1
1

answered Mar 04 '12 at 15:34

Jared Shaver

1,339
8
12

I read that `WSHttpBinding` supports SOAP 1.2, therefore a WSHttpBinding web service doesn't support BasicHttpBinding clients... – enzom83 Mar 04 '12 at 15:49
I believe that if you wanted to support both, you would need to configure two different Endpoints. – Jared Shaver Mar 04 '12 at 15:51
So should I configure a BasicHttpBinding additional endpoint dedicated to BasicHttpBinding clients? – enzom83 Mar 04 '12 at 15:54
It depends on what your requirements are. If you don't need the advanced functionality in WsHttpBinding, you could just support one Endpoint with BasicHttpBinding. – Jared Shaver Mar 04 '12 at 16:24
Otherwise, I should support one endpoint with WsHttpBinding and one endpoint with BasicHttpBinding. – enzom83 Mar 04 '12 at 16:36

What are the limitations of the BasicHttpBinding?

1 Answers1