Base64 is a MIME message encoding one of the ways commonly used.
Base64是MIME邮件中常用的编码方式之一。
There are two kinds of message encoding available in WSDL: literal and SOAP-encoding.
WSDL中有两种消息编码可用：literal和SOAP编码。
Defines a method that can import custom policy assertions for message encoding and that adds the binding elements that implement the policy.
定义一个方法，该方法可导入消息编码的自定义策略断言，并添加实现策略的绑定元素。
Those include functional modules, related data structure, frames of message encoding, certificate management database, ring of keys, concrete information flows for access control and so on.
完整设计了模型的整个可实现框架：包括各组成模块的功能、相关数据结构和消息编码格式、证书管理库和密钥环的设计，以及具体的访问控制流程等。
The actual encoding of the message itself (enveloping) is usually SOAP, but other encodings can be supported as well.
消息本身的实际编码方式(信封)通常是SOAP，但同时也支持其它编码。
Now I'll look at two ways of transmitting this model in a SOAP message; first of all by translation to the SOAP encoding, and then directly, encoding in RDF.
现在我来看看在SOAP消息中传输这种模型的两种方式：第一种是通过转换为SOAP编码来传输，另一种是直接以rdf编码来传输。
In addition, if the internal encoding exists and it is not a valid IBM encoding schema, the parser will issue a SQL16168N error message.
另外，如果内部编码虽然存在但却不是一个有效的IBM编码模式，解析器将会发出SQL 16168n错误消息。
The parsing time and space is related to the format (structure and encoding) of a message.
解析时间和空间与消息格式(结构和编码)有关。
The SOAP Data Handler supports encoding for parts defined using types, although the message parts must be in the order defined in the WSDL when using document style.
尽管当使用文档类型时，消息的部分必须遵循WSDL中定义的顺序，但SOAP数据处理器支持使用类型来对定义的部分进行编码。
The time it takes to handle the message: Specifically, the XML parsing, any flow management, invocation of the service, and the final response encoding.
处理消息所花费的时间：具体说来，是xml解析、任意流程管理、服务的调用以及最终响应编码。
The SOAP binding section in the WSDL definition determines the structure of the body in the SOAP message. It sets, among other properties, the operation style and the encoding mechanisms used.
在WSDL定义的SOAP绑定部分决定了 SOAP消息体的结构，它再其中设置了使用的操作方式和编码机制。
A typical SOAP message also can include the encoding style, which assists the recipient in interpreting the message.
典型的SOAP消息还可能包含编码风格，它帮助接收方解释该消息。
The first is the use of an XML message format for platform-agnostic encoding, and the second is the message structure, which consists of a header and a body.
第一个组件是使用XML消息格式进行平台无关的编码，第二个组件消息结构，包括消息头和消息体。
Literal encoding could simply involve some written prose documentation by the service author that states exactly what the message payload will look like.
文字编码可以只包括服务创始人编写的某个没有固定格式的文档，该文档精确地描述了有效负载的具体情况。
A SOAP message is basically an HTTP request and response that complies with the SOAP encoding rules.
SOAP消息实质上是一个遵循soap编码规则的HTTP请求和响应。
This also allows you to denote that the encoding of the images is binary (as opposed to the textual encoding of the main message).
这也允许你表示这个图片的编码是二进制的(与主要消息的文本编码方式相对)。
If an integer is four bytes in length with a big-endian encoding, then the message USES that same representation.
如果整数采用big - endian法编码、用四个字节表示，那么消息中也使用同样的表示。
The simplest solution for dealing with attachments is base-64 data encoding, which allows for placing attachments directly inside the SOAP message.
处理附件的最简单的解决方案是base- 64数据编码，它允许直接将附件放置在SOAP消息中。
The major difference between the two is that the first contains a schema that fully describes the SOAP messages, while the second needs extra encoding rules to serialize the data into a message.
两者之间的主要区别是前者包含一个模式(schema)，这个模式完整地描述SOAP消息，而后者需要额外的编码规则以便把数据序列化为消息。
The literal encoding simply means that the payload of a SOAP message is defined completely by a specific schema, often an XML schema.
文字编码仅表明SOAP消息的有效负载完全是由一个特定的模式(通常是XMLSchema)定义的。
If you have a string, in memory, in a file, or in an email message, you have to know what encoding it is in or you cannot interpret it or display it to users correctly.
如果你有一个字符串，在内存中，在文件中，或者在Email消息里，你必须知道它的编码是什么。否则你无法正确的解释或者显示给用户。
The format, encoding and coded character set of the message body are stored in the MQControl structure, contained in the MQ Header.
消息正文的格式、编码和编码字符集存储在MQControl结构中，并包含在MQHeader 中。
Moreover, these large messages often contain very large embedded binary information encoded using base-64 encoding as part of the main body of the XML message. This typically happens when a.
而且，这些大消息往往包含了非常大的、作为XML消息主体的、采用base- 64编码的二进制编码信息。
When the translator first opens the message file, those parts will be empty, and the translator must specify the character encoding he or she will use — in this case, Latin-1 — and the translations.
当翻译人员首次打开消息文件时，这些部分将为空，并且翻译人员必须指定要使用的字符编码(在本例中为Latin - 1)和翻译。
Listings 11 and 12 show the SOAP encoding of the GetResourceProperty message exchange.
清单11和12展示了GetResourceProperty消息交换的SOAP编码。
A message stereotype has a property to denote its assumed encoding form (for example, SOAP-literal, SOAP-rpc, ASN.1, and so on).
一个消息原型具有一个属性来表示它的假定的编码格式(例如SOAP -literal, SOAP - rpc, aSN . 1等等)。
It only differs in that the content of the SOAP message body contains extra type information that the encoding mechanism generates.
唯一不同的一点是，SOAP消息体的内容包含一些额外的类型信息，这是由编码机制生成的。
Architecturally, components interact via an abstract service model-a messaging model that resides at a level of abstraction above any particular protocol or message-encoding format.
架构上，组件通过一个抽象的服务模型(一个消息传递模型，位于任何特殊协议或消息编码之上的抽象层中)进行交互。
Among these eight ingredients, encoding and decoding are of special significance because communication is achieved by encoding a message into a signal and by decoding this signal at the receiving end.
在这八个成分中，编码和解码具有特别的意义，因为通信是通过将消息编码为信号并通过在接收端解码该信号来实现的。
The sooner you, as encoder, receive feedback in the form of a body language message, the sooner you can switch to a more effective encoding technique if necessary.
如果必要的话作为编码越早接收到一个肢体语言的反馈信息，就能越早切换到一个更有效的编码技术。
应用推荐