blocks|key|1641435|text|WCF确实有一个默认的有效负载大小限制，该限制将拒绝超过一定字节数的消息。当然，这是可以在配置文件的绑定部分进行配置的。下面是一个包含basicHttpBinding的粗略示例，它向您展示了许多可用的属性：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1641436|<bindings>
++++<basicHttpBinding>
++++++++<binding+name="testBinding"+maxReceivedMessageSize="2147483647">
++++++++++++<readerQuotas
++++++++++++++maxDepth="2147483647"
++++++++++++++maxStringContentLength="2147483647"
++++++++++++++maxArrayLength="2147483647"
++++++++++++++maxBytesPerRead="2147483647"
++++++++++++++maxNameTableCharCount="2147483647"+/>
++++++++</binding>
++++</basicHttpBinding>|code-block|syntax|javascript|1641437|其思想是，您可以创建许多不同的绑定，以用于不同的场景。这很好，因为您可以微调服务的使用方式，并且只增加需要它们的端点的消息大小限制。|1641438|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms731361.aspx^0|1V|G|1V|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

WCF does have a default payload size limit that will reject messages over a certain number of bytes. This is configurable of course in the binding section of your configuration file. Here is a crude example with a <a href="http://msdn.microsoft.com/en-us/library/ms731361.aspx" rel="nofollow noreferrer"><code>basicHttpBinding</code></a> showing you many of the attributes available to you:

<pre><code>&lt;bindings&gt;
 &lt;basicHttpBinding&gt;
 &lt;binding name="testBinding" maxReceivedMessageSize="2147483647"&gt;
 &lt;readerQuotas
 maxDepth="2147483647"
 maxStringContentLength="2147483647"
 maxArrayLength="2147483647"
 maxBytesPerRead="2147483647"
 maxNameTableCharCount="2147483647" /&gt;
 &lt;/binding&gt;
 &lt;/basicHttpBinding&gt;
</code></pre>

The idea is that you can create many different bindings that you can use for different scenarios. This is nice as you can fine tune how your services are consumed and only increase the message size limit for the endpoints that need them.

blocks|key|1426676|text|虽然像Andrew+Hare建议的那样使用绑定属性和readerQuotas将允许大多数实际用途基本上没有大小限制，但请记住，如果您接受一个长时间运行的命令，您将遇到其他问题，如超时，无论该服务是如何构造的(使用或不使用WCF+)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1426677|无论消息的大小如何，都需要对WCF服务进行性能调节，这样它就不会被淹没。如果您在IIS或WAS中托管它，您将在这些托管环境中拥有额外的内置功能，这些功能将使您的服务更加“高度可用”。但是，您仍然需要注意并发问题。下面的WCF配置提供了一个设置某些限制值的示例。|1426678|+++<system.serviceModel>

++++...

+++++<behaviors>
+++++++<serviceBehaviors>
+++++++++<behavior+name="GenericServiceBehavior">
+++++++++++<serviceTimeouts+transactionTimeout="00:09:10"/>
+++++++++++<serviceThrottling
+++++++++++++maxConcurrentCalls="20"
+++++++++++++maxConcurrentSessions="20"
+++++++++++++maxConcurrentInstances="20"
+++++++++++/>
+++++++++</behavior>
+++++++</serviceBehaviors>
+++++</behaviors>
+++</system.serviceModel>|code-block|syntax|javascript|1426679|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

While using the binding attributes and readerQuotas like Andrew Hare suggests will allow for essentially an unlimited size for most practical uses, keep in mind that the you will run into other issues such as timeouts if you accept a long running command, no matter how that service is constructed (using WCF or not). 

No matter what the size of your message is, the WCF service will need to be throttled for performance so that it is not flooded. If you are hosting it in IIS or WAS, you will have additional built-in features to those hosting environments that will make your service much more "highly available". However, you still need to pay attention to concurrency issues. The following WCF config provides an example of setting some throttling values.

<pre><code> &lt;system.serviceModel&gt;

 ...

 &lt;behaviors&gt;
 &lt;serviceBehaviors&gt;
 &lt;behavior name="GenericServiceBehavior"&gt;
 &lt;serviceTimeouts transactionTimeout="00:09:10"/&gt;
 &lt;serviceThrottling
 maxConcurrentCalls="20"
 maxConcurrentSessions="20"
 maxConcurrentInstances="20"
 /&gt;
 &lt;/behavior&gt;
 &lt;/serviceBehaviors&gt;
 &lt;/behaviors&gt;
 &lt;/system.serviceModel&gt;
</code></pre>

blocks|key|1641587|text|如果您使用的是NetTCPBinding或NetNamedPipeBinding，则可以使用MaxConnections属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1641588|<bindings>
++<netTcpBinding>
++++<binding+name="myTCPBinding"+maxConnections="15"/>
++</netTcpBinding>
</bindings>|code-block|syntax|javascript|1641589|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you're using NetTCPBinding or NetNamedPipeBinding you can use the MaxConnections property:

<pre><code>&lt;bindings&gt;
 &lt;netTcpBinding&gt;
 &lt;binding name="myTCPBinding" maxConnections="15"/&gt;
 &lt;/netTcpBinding&gt;
&lt;/bindings&gt;
</code></pre>

Lets assume that I'm dealing with a service that involves sending large amounts of data.

If I implement this with WCF, will WCF throttle the service based on how much memory each request takes to serve? Or will I be getting continuous out of memory exceptions each time I receive a large number of hits to my service?

I'm quite curious as to dealing with this problem outside of WCF, I'm still a bit new to service development...

WCF Service Throttling

让我们假设我正在处理一个涉及发送大量数据的服务。如果我用WCF实现这一点，WCF是否会根据每个请求需要多少内存来服务来限制服务？或者，每次我的服务收到大量命中时，我都会得到连续的内存不足异常？我很好奇在WCF之外处理这个问题，我对服务开发还是个新手……

问WCF服务限制
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF服务限制EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF服务限制
EN