I'll explore only the latter, authorized-push model.
我将只讨论后一种情况，即经过授权的push模型。
The main distinction made in models of interaction is between the pull model and the push model.
交互模型方面的主要区别是拉模型与推模型之间的区别。
It's ironic that the entire Web is on a push model, yet the browser-the most fundamental tool of interacting with the web-is on a pull model.
讽刺的是，整个互联网都属于push模型，但是浏览器，这个与网络交互的最根本的工具，却是pull模型。
The push model requires the content handlers to build very complex state machines.
推送模型要求内容处理程序生成非常复杂的状态机器。
To accurately reproduce the narrative in the output document, the style sheet must handle elements regardless of where they appear, and the push model excels at that.
为了在输出文档中准确地重现叙述，不管元素出现在哪里，样式表都必须处理它们，而推模型在这一方面比较擅长。
The distinction becomes easier to grasp if you think of action-based frameworks as using a "push" model, whereas component frameworks utilize a "pull" model.
如果将基于动作的框架想象为使用 “push”模型，而将组件框架想象为使用 “pull” 模型，那么这种区别就很容易理解了。
The user does not need to click anywhere or to perform any action at all; these alerts just appear when they arrive dynamically (a push-model).
用户根本不需要单击任何地方或执行任何操作；当这些警报以动态方式到达时，就会立即显示出来（一种“推送”模式）。
The user does not need to click anywhere or to perform any action at all; these alerts just appear when they arrive dynamically (a push-model).
用户根本不需要单击任何地方或执行任何操作；当这些警报以动态方式到达时，就会立即显示出来（一种“推送”模式）。
应用推荐