blocks|key|1261662|text|WCF使用SOAP消息，但使用哪种消息编码完全取决于您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1261663|基本上，开箱即用有两种编码方式:文本编码(+XML消息的文本表示)或二进制编码。如果确实需要，您可以编写自己的消息编码。|1261664|开箱即用，basicHttp和wsHttp绑定使用文本编码-但如果您愿意，也可以对其进行更改。默认情况下，netTcp绑定(这是企业防火墙背后的首选)将使用二进制。|1261665|如果您愿意，您还可以定义(仅在config中)您自己的“二进制http”协议：|1261666|+++<bindings>
++++++<customBinding>
++++++++<binding+name="BinaryHttpBinding">
++++++++++<binaryMessageEncoding+/>
++++++++++<httpTransport+/>
++++++++</binding>
++++++</customBinding>
++++</bindings>|code-block|syntax|javascript|1261667|然后在您的服务和客户端配置中使用它：|1261668|+++<services>
++++++<service+name="YourService">
++++++++<endpoint
++++++++++address="http://localhost:8888/YourService/"
++++++++++binding="customBinding"
++++++++++bindingConfiguration="BinaryHttpBinding"
++++++++++contract="IYourService"
++++++++++name="YourService"+/>
++++++</service>
++++</services>|1261669|现在您有了一个基于http的传输协议，它将以紧凑的二进制编码您的消息，供您使用和享受！|1261670|不需要额外的编码或繁琐的hack或大量的手动XML序列化代码-只需将它们连接在一起并使用即可！啊，WCF灵活性的乐趣！|1261671|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

WCF uses SOAP messages, but what kind of message encoding is used, is totally up to you. 

Basically, out of the box, you have two: text encoding (text representation of XML message) or binary encoding. You can write your own message encoding, if you really must and need to.

Out of the box, the basicHttp and wsHttp bindings use text encoding - but you can change that if you want to. The netTcp binding (which is the clear preferred choice behind corporate firewalls) will use binary by default.

You can also define (just in config) your own "binary http" protocol, if you wish:

<pre><code> &lt;bindings&gt;
 &lt;customBinding&gt;
 &lt;binding name="BinaryHttpBinding"&gt;
 &lt;binaryMessageEncoding /&gt;
 &lt;httpTransport /&gt;
 &lt;/binding&gt;
 &lt;/customBinding&gt;
 &lt;/bindings&gt;
</code></pre>

and then use it in your service and client side config:

<pre><code> &lt;services&gt;
 &lt;service name="YourService"&gt;
 &lt;endpoint
 address="http://localhost:8888/YourService/"
 binding="customBinding"
 bindingConfiguration="BinaryHttpBinding"
 contract="IYourService"
 name="YourService" /&gt;
 &lt;/service&gt;
 &lt;/services&gt;
</code></pre>

Now you have a http-based transport protocol, which will encode your message in compact binary, for you to use and enjoy!

No additional coding or messy hacks or lots of manual XML serialization code needed - just plug it together and use it! Ah, the joy of WCF flexibility!

blocks|key|1476278|text|二进制编码器不会以二进制格式序列化您的对象，因为它根本与序列化无关！它是在较低层工作的东西，并决定如何在服务器和客户端之间传输消息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476279|换句话说，对象将首先被序列化(例如，通过DataContractSerializer+)，然后被编码(通过BinaryEncoder)。因此，只要涉及到DataContractSerializer，您的对象就始终是XML格式。|1476280|如果您想要更紧凑的数据和更好的性能，请阅读此博客：|1476281|https://blogs.msdn.microsoft.com/dmetzgar/2011/03/29/protocol-buffers-and-wcf/|offset|length|1476282|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|26|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@$H|U|I|V|1|W]]|A|$]]|$1|J|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|G]]]]

The binary encoder will NOT serialize your object in binary, because it has nothing to do with serialization at all! It is something working at a lower layer and decides how message is transported between server and client.

In other words, the object will first be serialized (by DataContractSerializer, for example) and then encoded (by BinaryEncoder). So your object will always be in XML format as long as DataContractSerializer is involved.

If you want a more compact data and better performance, read this blog:

<a href="https://blogs.msdn.microsoft.com/dmetzgar/2011/03/29/protocol-buffers-and-wcf/" rel="nofollow noreferrer">https://blogs.msdn.microsoft.com/dmetzgar/2011/03/29/protocol-buffers-and-wcf/</a>

blocks|key|1476333|text|下面是一个如何在https://www.codeproject.com/Articles/434665/WCF-Serialization-A-Case-Study中进行自定义编码的示例|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1476334|值得注意的是，实际发送的内容与使用默认编码发送byte[]的服务方法相同。无论您如何配置序列化，通过网络传输的消息仍然使用SOAP+XML信封。|1476335|它看起来是这样的：|1476336|POST+http://127.0.0.1:12345/forSwerGup182948/Client+HTTP/1.1
Content-Type:+text/xml;+charset=utf-8
VsDebuggerCausalityData:+uIDPo%2BWkoDpet/JOtGlW%2BEHdpDQAAAAAvFs5XOJ0tEW0wTvNVRDUIiabR6u%2Bp%2BJNnd5Z%2BSWl1NcACQAA
SOAPAction:+"http://tempuri.org/ITransmissionService/SendData"
Host:+127.0.0.1:12345
Expect:+100-continue
Accept-Encoding:+gzip,+deflate
Content-Length:+2890

<s:Envelope+xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><SendData+xmlns="http://tempuri.org/"><message>eyI8Q2FsbGJhY2tJZD5rX19CYWNraW5nRmllbGQiOiJlYTQ3ZWIzMS1iYjIzLTRkODItODljNS1hNTZmNjdiYmQ4MTQiLCI8RnJvbT5rX19CYWNraW5nRmllbGQiOnsiPENoYW5uZWxOYW1lPmtfX0JhY2tpbmdGaWVsZCI6Ikdyb3VwMSIsIjxOYW1lPmtfX0==</message></SendData></s:Body></s:Envelope>|code-block|syntax|javascript|1476337|entityMap|0|LINK|mutability|MUTABLE|url|https://www.codeproject.com/Articles/434665/WCF-Serialization-A-Case-Study^0|8|22|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Here is an example of how to make custom encoding here <a href="https://www.codeproject.com/Articles/434665/WCF-Serialization-A-Case-Study" rel="nofollow noreferrer">https://www.codeproject.com/Articles/434665/WCF-Serialization-A-Case-Study</a>

It's worth noting that what actually gets sent is the same as if you had a service method sending byte[] with default encoding. The message going over the wire still uses a SOAP XML envelope regardless of how you configure serialization. 

It looks like this:

<pre><code>POST http://127.0.0.1:12345/forSwerGup182948/Client HTTP/1.1
Content-Type: text/xml; charset=utf-8
VsDebuggerCausalityData: uIDPo+WkoDpet/JOtGlW+EHdpDQAAAAAvFs5XOJ0tEW0wTvNVRDUIiabR6u+p+JNnd5Z+SWl1NcACQAA
SOAPAction: "http://tempuri.org/ITransmissionService/SendData"
Host: 127.0.0.1:12345
Expect: 100-continue
Accept-Encoding: gzip, deflate
Content-Length: 2890

&lt;s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"&gt;&lt;s:Body&gt;&lt;SendData xmlns="http://tempuri.org/"&gt;&lt;message&gt;eyI8Q2FsbGJhY2tJZD5rX19CYWNraW5nRmllbGQiOiJlYTQ3ZWIzMS1iYjIzLTRkODItODljNS1hNTZmNjdiYmQ4MTQiLCI8RnJvbT5rX19CYWNraW5nRmllbGQiOnsiPENoYW5uZWxOYW1lPmtfX0JhY2tpbmdGaWVsZCI6Ikdyb3VwMSIsIjxOYW1lPmtfX0==&lt;/message&gt;&lt;/SendData&gt;&lt;/s:Body&gt;&lt;/s:Envelope&gt;
</code></pre>

I have a client-server application, which communicates using WCF, and uses NetDataContractSerializer to serialize the objects graph. 

Since a lot of data is transferred between the server and the client, I tried to decrease its size by fine tuning the size of the data members (e.g. changed int to short, long to int, etc.). 

After finishing the tuning, I found out, that the amount of transferred data hasn't changed! The problem is, that the NetDataContractSerializer serializes the objects graph to XML, so no matter what's the size of the data-member, the only thing that matters is the size of its value. For example, the value 10023 of a Int16 data member will be serialized as the string "10023" (0x3130303233), instead of just 10023 (0x2727).

I remember that in Remoting I could use the BinaryFormatter which serialized the values according to the type of the data member, but I don't know if it's possible to use it with WCF.

Does someone have a solution?

Serialize WCF message in a binary way, and not as a SOAP Message

服务器

防火墙

我有一个客户端-服务器应用程序，它使用WCF进行通信，并使用NetDataContractSerializer来序列化对象图。由于大量数据在服务器和客户端之间传输，我尝试通过微调数据成员的大小来减小其大小(例如，将int更改为short，将long更改为int，等等)。完成调优后，我发现传输的数据量并没有变化！问题是，...

问以二进制方式序列化WCF消息，而不是将其序列化为SOAP消息
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问以二进制方式序列化WCF消息，而不是将其序列化为SOAP消息EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问以二进制方式序列化WCF消息，而不是将其序列化为SOAP消息
EN