We defined 10,000 users for this test.
我们这个测试定义了10,000个用户。
We defined three channels and four components.
我们定义了三个通道、四个组件。
We defined 7000 users for Domino 6.5, and 10,000 for Domino 7.0.
我们为Domino 6.5定义了7000个用户，为Domino 7.0定义了10,000个用户。
We defined these possible combinations in three different input criteria.
我们用三个不同的输入条件定义了这些可能的组合。
We defined a method named double that takes an Int argument and returns Unit.
我们定义了一个方法叫double，接受一个Int参数，返回unit。
Figure 4 shows the security constraint we defined for our form-login page
图4显示了在表单登录页面上定义的安全约束
And we defined the overall size of the animal - as yea big — we called that "s."
我们把这个动物的总尺寸，定义为大的-，我们称体积为“s。”
We defined a basic process, according to the XP principles, and then started work.
我们根据XP的原则定义基本的流程，并开始工作。
As we defined in the profile, all these tables will be stored in the same tablespace.
与配置文件中定义的一样，所有这些表将存储在同一表空间中。
Figure 5 shows the security constraint we defined for the SecureServlet Web resource.
图5显示了为SecureServletWeb资源定义的安全约束。
We defined the differences between Live Application Mobility and Live Partition Mobility.
我们定义了动态应用程序迁移和动态分区迁移之间的区别。
In one case, we defined a 25-page coding standards document that almost no one followed.
有一次，我们定义了几乎没人遵守的25页的编码标准文档。
The constraints we defined represent just a small sample of the validation that Grails offers.
我们定义的约束只代表了Grails提供验证的小部分例子。
During the creation of the filesystems, we defined that they should not automatically be mounted.
在创建文件系统的过程中，我们定义不自动挂载它们。
In our design, we defined three personas: the typical customer, a group leader, and an administrator.
在我们的设计中，定义了三种角色：典型客户、组负责人和管理员。
In those days we defined "everyone else" as people in our high school or people who listened to WPLJ.
在那时候，我们这样定义“每个人”：在我们的高中或者听了WPLJ的人们。
However, while we defined a root and addTask screen, there is no way to get from one to the other.
然而，尽管我们定义了root和addTask屏幕，但没有办法从一个屏幕跳转到另一个。
We defined support for JMS messaging as one of the core requirements toward our ESB solution in Part 3.
我们定义了对JMS消息传递的支持，并将其作为第3部分中的ESB解决方案的核心需求之一。
We defined an accredited investor as someone who can participate in a DPP or other sophisticated programs.
我们把可信投资者定义为,有资格加入DPP或者其他复杂项目的人
In our case, we defined everything on HADB1 and then synchronized the definition to the other server HADB2.
本例中，我们在HADB1上定义了所有一切，然后使另一台服务器HADB2上的定义同步。
You should see by default the schema name ASN1 since this is the schema name we defined in our profile.
在默认情况下，您应该看到模式名称ASN1，因为它是我们在配置文件中定义的模式名称。
As shown in Listing 4, at the top of our base stylesheet (base.css) we defined the styles, including the font size.
如清单4所示，我们在基本样式表(base . css)的顶部定义了样式，包括字体大小。
Notice that in print.php we defined our own PHP function, called print_sequence(), in the section of the HTML page.
注意，在print.php 中，我们在HTML页面的部分定义了自己的名为 print_sequence() 的PHP函数。
When it is returned to the browser it will specify the IMT that we defined when we added the resource to the system.
当它被返回到浏览器时，它会指定我们把资源添加到系统时所定义的IMT。
Next, we defined a role named authenticated_user, which groups all users that have been authenticated by the system.
接下来，我们再定义一个名为 authenticated_user 的角色，该角色将已经通过系统身份验证的用户归为一组。
When we defined our content spot above, we defined it to be populated with content from our layouts content resource.
当我们定义上面的内容点时，定义使用layouts内容资源的内容对它进行填充。
SaaS meets one criteria we defined for a service - we want to pay a fair price to use them and we don't want to own them.
SaaS满足了我们定义服务的一个准则——我们通过付费用去使用服务而并不想拥有服务。
First, you need to get an overview of everything we defined as mapping from any of our data sources to the federated model.
首先，你需要有一个数据源到联邦模型的整体视图。
In this step, we establish the relationship between the security roles that we defined previously and their authentication status.
在这一步里，我们建立了前面定义的安全角色和他们的身份验证状态之间的关系。
In this step, we establish the relationship between the security roles that we defined previously and their authentication status.
在这一步里，我们建立了前面定义的安全角色和他们的身份验证状态之间的关系。
应用推荐