Please read this message carefully.
请仔细阅读该消息。
When you read this message, I shall be in Argentina.
当您读这则消息，我将是在阿根廷。
I have read and re-read this message several times, and each time I discover something new.
我一再重复阅读这个信息好几次，每一次我都会发现一些新的东西。
Upon opening it, Dad read this message: "You've been like a father to me." he looked at Ryan, puzzled.
父亲打开贺卡，读上面的祝福语：“你待我如父亲一般。”父亲看着赖安，愣住了。
Part 3 of this series of articles explained how to read and change message payloads using a mediation.
本系列文章的第3部分阐述了如何使用中介阅读和更改消息有效负载。
Because nonblocking channels give no indication when a message has been fully read, we are forced to handle this at the protocol layer.
因为当全部读取消息时，非阻塞通道没有给出任何提示，所以强制我们在协议层处理这一情况。
A mediation could read the content of a message and, based on this content, route the message to different destinations.
中介能够读入消息的内容，基于这一内容，将消息路由到不同的目的地。
This seems not very useful on the surface — what good is an encrypted message that anyone can read?
乍看上去这似乎没什么用 —任何人都可以读取的加密消息有什么用？
If the message was successfully deleted, the report contains this information, noting whether or not the message was read.
如果消息被成功删除，该报告将包含此信息，并说明邮件是否被阅读。
This will assure that nobody can read the message that is send over a public network.
这将确保没有人能够读取通过公共网络发送的消息。
The result of this is a message that can be read as a text message from any MQ client application.
最后得到的是可以从任何MQ客户机应用程序作为文本消息读取的消息。
This buffer caches JMS message data that may otherwise need to be read from disk.
该缓冲区缓存原本需要从磁盘读取的JMS消息数据。
After adding this ARIA tag, when the window opens, screen readers such as JAWS 10 will be aware of it and can read the message to the users.
添加此aria标记之后，当窗口打开时，JAWS10等屏幕阅读器将能够察觉此事件，并且能够将消息读给用户。
This is my message to you tomorrow (Do not Read), only to see tomorrow!
这是我给你明天的信息(别往下看)，明天才看！
This is essentially a technique by which part of a record or file can be read into WebSphere Message Broker and processed.
这实质上是一种技术，通过该技术可以将部分记录或文件读取到WebSphereMessageBroker并进行处理。
Following good mediation handler practices, we read this string from a context property, and use it to generate a new message.
遵循良好的中介处理程序实践，我们从上下文属性中读取此字符串，并且用它来生成新的消息。
This ability to reach into the enterprise means that no matter where data is staged, it can be read or written by Message Broker with the minimum of fuss.
这种延伸到整个企业中的能力意味着，无论数据驻留在何处，MessageBroker都可以毫不费力地读写该数据。
Such a message is probably of limited use, although it can be read back in at a corresponding input node, in this case an MQInput node with the SOAP domain selected.
这样的消息也许只有有限的用途，虽然可以在对应的输入节点中将其读回，在此情况下，将选择带soap域的MQInput节点。
As we've explained at the beginning of this section we want to read a file from the file system and use ServiceMix to send an E-mail message using the file contents to a certain E-mail address.
我们在本节一开始就已经说过，我们要从文件系统中读取一个文件，然后使用ServiceMix把包含文件内容的电子邮件消息发送到某个电子邮件地址。
To work with this example we will use an Mail client to send a message, and use the Mule POP3 transport to read the message from the Mail server.
为了演示这个示例，我们将使用邮件客户端发送邮件，并使用MulePOP3传输（Transport）读取来自邮件服务器的消息。
To read the message from the queue (which in this case ultimately involves reading from the file system since we use the JNDI identifier for the file system), use the code in Listing 11.
要从队列中读取消息(在本例中最终涉及到从文件系统中读取数据，因为我们使用文件系统的JNDI标识符)，使用清单11中的代码。
This map allows you to convert one type of message into another type using an easy-to-read graphical interface, as shown in Figure 1.
该映射允许您使用易于阅读的图形界面将一种类型的信息转化为另一种类型，如图1所示。
But in this case, it first tries to read a message from the input stream, and it will block until something is received.
但是，在这里，它首先尝试从输入流读一条消息，并阻塞直到收到消息。
In this article, we will take the practice approach of using SDO to read and write the contents of a message within a mediation.
在本文中，我们将采用实际方法在中介中通过SDO阅读和撰写消息内容。
"And when you want to read a secret invisible message," said Sam, "you push the hair-dryer button on this part of the machine, and..."
“如果你想要阅读这条隐形的秘密。”萨姆说，“请打开吹风机的按钮吹一下，然后…”。
This can be contrasted with a stream socket, where if the sender wrote a 100 byte message, the receiver could read it in two chunks of 50 bytes or 100 chunks of one byte.
对比字符流，当发送者发送100字节时，接收者可以选择接受分两次，每次50字节进行接受，还是一次性接受100字节。
This can be contrasted with a stream socket, where if the sender wrote a 100 byte message, the receiver could read it in two chunks of 50 bytes or 100 chunks of one byte.
对比字符流，当发送者发送100字节时，接收者可以选择接受分两次，每次50字节进行接受，还是一次性接受100字节。
应用推荐