The ShippingTask interface needs one request response operation, shipOrder, which takes an Order business object as input.
ShippingTask接口需要一个请求-响应操作shipOrder，该操作以一个Order业务对象作为输入。
If immediate response is needed, is there any need to "remember" the order of requests or is each one independent of the others?
如果需要立即响应，那么是否需要“记住”请求发送的顺序或者要求请求间没有相互依赖性呢？
Or possibly it fires more than one response message to the client as we see in the book ordering process, where one message confirms the order, another message indicates dispatch of the order.
或者它可能会给客户端发回多个响应消息，正如你在订书过程中看到的，其中一个消息确认订单，另一个消息指明订单的派发。
Note that between the last article and this one, in order to keep the file sizes relatively manageable, I've broken the request/response types out into their own file.
注意，在这最后一篇文章中，为了使文件大小保持在相对合理的范围内，我将请求/响应类型分开放到不同的文件中。
But one can imagine other situations where the disaster response is crowdsourced, and maybe the crowd is some combination of people in-country and out-of-country in order to get the fastest results.
但是你可以想象其它众包救灾的情况，也许就是一些把国内外人民结合的方式获得最快的成效。
The response you received is an automated one that our system sends out once an order has been placed on the site.
因此你上次的定单是完不成了，你收到的回应是系统自动回复的。
The response you received is an automated one that our system sends out once an order has been placed on the site.
因此你上次的定单是完不成了，你收到的回应是系统自动回复的。
应用推荐