Let me jump in and do the work as we discussed.
让我投入进去并且做好我们所讨论的工作。
In other words, better capacity as we discussed earlier to deal with difficulties.
换句话说,就是我们之前提及的有更强的应对困难的能力。
For this reason, changes to their reference set must be tracked, as we discussed in Write barriers.
出于这个原因,必须跟踪对它们的引用设置的更改,如写入屏障一节所述。
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.
即,消息传递引擎将根据我们前面讨论的连接标识对此队列进行访问授权。
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角色终究只是一个名称,是可以绑定到任何一组主体的逻辑构造。
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。
And as we discussed in the first post in this series, much of that data is structured - allowing it to be inter-connected and re-used by third parties.
正如我们在专题的第一篇文章中讨论过的,越来越多的数据正在结构化——允许第三方开发者交叉连接和利用这些数据。
You can use gateway form and activity form interchangeably for process models that contain only control flow, as we discussed in the Background section in Part 1 of this article.
流程模型中的网关形式和活动形式可以互换使用,如本文第1部分中的背景部分所述。
However, as we discussed above, specialisations of modelling languages (like SoaML) can certainly help to make the process of documenting some types of architectures more straightforward.
然而,就像我们上面所讨论的,定制型的建模语言(如SoaML)肯定有助于让记录某些架构类型的过程更加直截了当。
Even though this scenario isn't included in the sample code available for download with this article, the approach to executing such a query is the same as we discussed in previous examples.
即使该场景没有包含可供本文下载的样例代码,但是执行此类查询的方法与我们在前面例子中讨论的方法是相同的。
But control code on Windows and requests on Linux are defined in such a different way that there is no fixed rule to find the mapping relations between these two parameters, as we discussed earlier.
但是Windows的控制代码和Linux的请求在定义上差别很大,以致没有固定规则能够找出这两个参数的映射关系,如前文所述。
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.
正如我们昨天在“巴厘岛早餐会”上所讨论的,我们必须要加强碳市场。
As we discussed in previous articles, the first step to becoming smarter is through instrumentation.
正如我们在前几篇文章中讨论的一样,实现智能化的第一步是实现仪表化。
As we discussed in the previous section, the first half of a rule definition is an Eclipse extension.
正如我们在前一小节中所讨论的那样,一个规则定义的前一半是一个Eclipse扩展。
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上调用,也可以通过代理调用。
As we discussed in the previous section, ISAPI filters can be created to respond to the events raised by IIS.
正如上一部分所讨论的,可以创建ISAPI筛选器以响应IIS引发的事件。
As we discussed during the configuration stage instead of having 2 IBM Cognos 8 environments we only have one.
正如我们在配置阶段所讨论的,我们不是具有2个,而是只有一个IBMCognos8环境。
As we discussed earlier, Seam is the only web framework today that supports lazy loading correctly for web applications.
正如我们前面所讨论过的,Seam是现今唯一一个正确支持Web应用延时加载的Web框架。
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 previous section, each log file created will have the same allocation of space based upon the logfilsiz parameter.
正如我们在前一节中讨论的,根据logfilsiz参数为所创建的每个日志文件分配相同的空间。
As we discussed earlier, one of the joys of working in software is the ability to build complex systems limited only by your imagination.
正如我们早先所讨论的,做软件工作的乐趣之一就是如果你的想象力无限,你将可以创建出任何复杂的系统。
As we discussed in Part 2 of this series, agents use connectors and protocol adapters to communicate with NMS applications or distributed services.
正如在本系列第2部分中所讨论的,代理可以使用连接器和协议适配器来与NMS应用程序或分布式服务进行通信。
As we discussed last time, meeting with a vendor to discuss a proposal is partly about getting information and partly about negotiating a good deal.
你会见供货商讨论计划时,一部分是获得新信息,一部分是协商新的交易。
应用推荐