Out of that pops the velocity, as we discussed.
除此之外是速度，如我们讨论过的那样。
Let me jump in and do the work as we discussed.
让我投入进去并且做好我们所讨论的工作。
As we discussed in Part 1, classloaders use a tree-structured hierarchy.
正如我们在第1部分中讨论的，classloader使用一个树状层次结构。
As we discussed earlier, the CBE is the accepted standard for such a structure.
正如前面讨论的，CBE是被广泛接受的此类结构的标准。
As we discussed at the Bali Breakfast yesterday, we need to strengthen carbon markets.
正如我们昨天在“巴厘岛早餐会”上所讨论的，我们必须要加强碳市场。
In other words, better capacity as we discussed earlier to deal with difficulties.
换句话说，就是我们之前提及的有更强的应对困难的能力。
As we discussed in the previous section on flow control objects, there are several ways to do this.
像我们前面讨论过的流控制对象一样，有多种方法可以获取对servletcontext类型的对象的引用。
As we discussed in previous articles, the first step to becoming smarter is through instrumentation.
正如我们在前几篇文章中讨论的一样，实现智能化的第一步是实现仪表化。
As we discussed in the previous article, unsealed AuthBundles may be vulnerable during serialization.
正如前一篇文章中讨论的，未密封的AuthBundles在串行化期间可能受损。
As we discussed in the previous section, the first half of a rule definition is an Eclipse extension.
正如我们在前一小节中所讨论的那样，一个规则定义的前一半是一个Eclipse扩展。
For this reason, changes to their reference set must be tracked, as we discussed in Write barriers.
出于这个原因，必须跟踪对它们的引用设置的更改，如写入屏障一节所述。
Maybe you encourage me to eat an extra meal there, but as we discussed, is that a profitable extra meal?
也许你会鼓励我再吃点其他东西，但正如我们之前所讨论的，这个加餐有利润吗？
As we discussed yesterday, God wants more than just a little piece of your heart. He wants your whole heart.
就想我们昨天讨论过的那样，上帝不是想仅仅在你心里占有一席之地。他想占据你整个心。
As we discussed last month, stateless session beans are well designed for e-business on demand applications.
正如我们上个月讨论的，无状态会话bean是为电子商务随需应变(e - businesson demand)应用程序精心设计的。
As we discussed, an MXBean's methods may either be called directly on a local MXBean or else through a proxy.
正如前面讨论过的，MXBean的方法既可以直接在本地MXBean上调用，也可以通过代理调用。
Creating semantic Web services via a logic deduction is almost impossible, as we discussed in this paper.
正如在本文前面讨论的，通过逻辑推理创建语义Web服务几乎是不可能的。
As we discussed during the configuration stage instead of having 2 IBM Cognos 8 environments we only have one.
正如我们在配置阶段所讨论的，我们不是具有2个，而是只有一个IBMCognos8环境。
As we discussed in the previous section, ISAPI filters can be created to respond to the events raised by IIS.
正如上一部分所讨论的，可以创建ISAPI筛选器以响应IIS引发的事件。
But never require a cookie to display the page, as we discussed earlier, or the spider won't be able to index it.
但是，正如前面讨论的，显示页面应该不需要cookie，否则爬行器无法将它编入索引。
The services have been assigned different types of usage models for demonstration purposes, as we discussed earlier.
正如我们先前讨论过的那样，服务根据不同的演示目的被分配了不同类型的使用模型。
That is, the messaging engine authorizes access to the queue based on the connection identity as we discussed earlier.
即，消息传递引擎将根据我们前面讨论的连接标识对此队列进行访问授权。
As we discussed earlier, Seam is the only web framework today that supports lazy loading correctly for web applications.
正如我们前面所讨论过的，Seam是现今唯一一个正确支持Web应用延时加载的Web框架。
This set of properties is often associated with an item class, as we discussed in the answer to the previous question.
正如在回答前面的问题时所讨论的那样，这组属性通常与一个项目类相关联。
After all, as we discussed earlier, a J2EE role is merely a name, a logical construct that can be bound to any set of principals.
正如我们前面所讨论的，J2EE角色终究只是一个名称，是可以绑定到任何一组主体的逻辑构造。
As we discussed earlier, one of the joys of working in software is the ability to build complex systems limited only by your imagination.
正如我们早先所讨论的，做软件工作的乐趣之一就是如果你的想象力无限，你将可以创建出任何复杂的系统。
In all other respects, these files are nearly the same as we discussed in the previous article, so we won't describe them again here.
这些文件的其它所有方面与我们在上篇文章中讨论的几乎相同，所以这里我们就不再描述了。
A better solution would be to place the repeating activities within a cycle, as we discussed in Scenario 2 in Part 1 of this article.
一个更好的解决方案是将重复的活动放在一个循环中，如本文第1部分中的场景2。
As we discussed in the previous section, each log file created will have the same allocation of space based upon the logfilsiz parameter.
正如我们在前一节中讨论的，根据logfilsiz参数为所创建的每个日志文件分配相同的空间。
As we discussed a couple of months ago, most of us, even the most ardent food lover, have at least one food that they just can't bear.
由几个月前的讨论发现，我们之中的大多数，即便是狂热的食物爱好者，也至少有一种食物是不能忍受的。
As we discussed in the XMBuilder section, your builder should register interest in those projects by returning them from the build method.
如同我们在XMBuilder一节所讨论的那样，构建器应该通过从build方法返回对那些项目感兴趣的内容来注册它们。
应用推荐