这一过程能使您确定消息的发送者以及消息在传递途中是否被修改过。
This process enables you to determine both who sent the message and whether it changed en route.
在您的动态消息。
如果没有足够的硬盘空间来传递消息，或者您的公司使用路由器控制来限制在环境中发送的消息的大小，那么这会造成问题。
This can cause problems if there is not enough disk space to transfer the message or if your company USES router controls to limit the size of messages sent in the environment.
例如，如果您拷贝一个消息，它们就会显示在最初生命线的底端。
For example, if you copy messages, they appear at the bottom of the original lifelines.
您很快在纸上写下这条消息并把它装在写有地址的信封里。
You jot down your message on a piece of paper and stuff it in an addressed envelope.
可将消息异步发送并放置在一个消息队列或堆上，直至您准备 “处理”它们。
Messages can be sent asynchronously and placed in a message queue or pile until you are ready to "process" them.
在测试消息流之前，您需要配置它。
在本示例中，您更改了记录的消息的详细内容的级别。
In this example, you changed the level of detail of a message that is logged.
除了可通过API在您自己的时间表中发布和删除消息之外，您还可以通过API来管理关注者名单。
In addition to Posting and removing messages to your own timeline through the API, you can also manage follower relationships through the API.
在清单1和清单2中，您已经看到过这些消息的主体。
You've already seen the bodies of these messages, in Listing 1 and Listing 2.
在您代码内的主决策点放几条这样的跟踪消息会有令人吃惊的帮助效果。
Placing a few such trace messages at major decision points in your code can be surprisingly helpful.
如果您输入错误的值，通道在启动时失败，错误消息写入通道两端的错误日志。
If you input incorrect values, the channel fails at startup, and error messages are written to the error log at both ends of the channel.
您需要将接收到的消息存储在portletsession类型的对象中。
You need to store the received message in an object of type PortletSession.
在Status视图中，您应该看到确认消息。
Roo还提供了一个选项，可以在您的应用程序中嵌入Twitter消息、文档、股票行情，地图，照片和视频流。
Roo also provides you an option to embed Twitter messages, documents, stock tickers, maps, photos, and video streams in your application.
在本示例中，您会找到定义输入消息(operation1Request)的操作(operation1)。
In this example, you find the operation (operation1), which defines the input message (operation1Request).
首先要进行检查，看看传入消息body定义的词是否在您的字典中。
Start by checking to see whether the word defined by the incoming message body is a word in your dictionary.
然后在选择这个子集时您会收到一条错误消息。
Then you will receive an error message when selecting this subset.
好消息是，您只需在自己的DB 2服务器上执行这些命令，而不必在任何DB 2客户机上执行这些命令。
The good news is that you only have to perform these commands on your DB2 server, not on any DB2 client machines.
您应该看到一个陷阱到达，您可以在您的陷阱接收器中打开该消息。
You should see a trap arrive, and then you can open the message in your trap receiver.
现在，在您导出示例时，您可以提供此提示文件，且您的数据包括在已导出的消息中。
Now, when you export examples, you can supply this hints file, and your data is included in the exported messages.
您现在已经使用ltpa令牌在消息级别上确保了请求者和提供者的安全。
You have now secured both the requester and the provider with LTPA token at the message level.
您的消息传递框架必须能够在一组应用和企业资源之间进行通信。
Your messaging framework must be able to communicate across an array of applications and enterprise resources.
首先是对企业消息传递的概述，在此我们将着眼于消息传递在您企业中所扮演的角色，并在建立可靠的通信方面给出了一些挑战。
We'll start with an overview of enterprise messaging, where we'll look at the role of messaging in your enterprise, as well as some of the challenges in establishing reliable communication.
这些消息也可以显示在您的个人地图上。
在以后的文章中，我们将向您展示当消息从总线中经过时，如何利用中介进行操作。
In an upcoming article, we will show you how you can manipulate a message as it flows through the bus using mediations.
在本文的示例中，您更改了在物理层实现消息路由的假设和做法，并将其向上移动到了逻辑层中，并在那里由集群进行管理。
In this example, you changed the assumption and practice of implementing message routing at the physical layer and moved it up into a logical layer where it is managed by the cluster.
继续在向导中进行单击，直到在您的工作空间中创建了一个新的消息设置项目。
Click through the wizard and a new message set project is created in your workspace.
如果您的MDB在您已经处理了它的主体后再次发送该消息，实际上您发送的是一个新的消息。
If your MDB resends the message after you had manipulated its body, you are actually sending a new message.
例如，通过在您的数据服务中设置某个缓存消息头，您可以将浏览器作为一个自由缓存使用。
For example, by setting certain caching headers in your data services, you can use the browser as a free cache.
应用推荐