显然，任何轮询类型的解决方案都是对端点的更改，但对WS-RM逻辑本身的更改应该最少。
Obviously, any kind of polling solution is a change to the endpoints but the change to the WS-RM logic itself should be minimal.
此方案的优势在于，虽然请求方仍然必须知道使用了某种类型的轮询机制，但服务本身并不必如此。
The advantage of this scenario is that while the requester must still know that some type of polling mechanism is being used, the service itself doesn't.
FOREST是由纯get或Web轮询用例引申而来的REST模式，包括某些特定类型的混搭，比如feed聚合或筛选器，为其它网页创建摘要的站点，等等。
FOREST is a REST Pattern derived from GET-only or polling Web use-cases, including certain kinds of mashups for e.g. feed aggregators or filters, sites that create summaries of other Web pages etc.
该适配器既可以配置为仅轮询特定类型的文件，也可以配置为仅轮询在特定时间段内创建的文件。
The adapter can be configured to poll for only certain types of files, or for files created during a certain time period.
目前存在多个轮询解决方案以及各种规范，这种现象清楚地说明了人们迫切地需要这种类型的解决方案。
There are already several polling solutions popping up various specifications, so clearly there is a need for this type of solution.
因而，轮询收集器通常使用粘附跟踪程序类型：apm系统在生成报告时将假定所有轮询事件之间的值不变。
Accordingly, polling collectors typically use sticky tracer types: the APM system reports the value as unchanged in between all polling events. Figure 4 illustrates this pattern.
因为不存在Comet的标准，让我们区别来看两种不同类型的Comet实现：长轮询与流式查询。
Since there is no Comet standard as such, let's distinguish between two types of Comet implementations: long-polling and streaming.
所有服务端和客户端实现必须支持“长轮询”连接类型，并且应该支持“回调轮询”。其他连接类型都是可选的。
All server and client implementations MUST support the "long-polling" connection type and SHOULD support "callback-polling". All other connection types are OPTIONAL.
UPMA协议对不同的业务类型赋予不同的优先级，并用轮询方式妥善地安排节点的分组传输；
UPMA protocol endows different priority levels to different types of traffic, and can perfectly schedule the transmission of mobile terminals (MTs) by means of polling.
UPMA协议对不同的业务类型赋予不同的优先级，并用轮询方式妥善地安排节点的分组传输；
UPMA protocol endows different priority levels to different types of traffic, and can perfectly schedule the transmission of mobile terminals (MTs) by means of polling.
应用推荐