操作的粒度是一项重要的设计要点。
我应如何决定用例粒度的正确层次?
How will I determine the right level of use case granularity?
一个关键设计决策是汇总表的粒度。
保护XML的基本粒度单位是元素。
The basic unit of granularity for securing XML is an element.
您可以选择评审日志的颗粒度级别。
You can choose a level of granularity for the reviews you log.
使用流策略支持发布的颗粒度。
Use the stream strategy to support the granularity of distribution being undertaken.
为数据访问对象定义最适合的粒度。
Define the most appropriate granularity for data access objects.
关于粒度管理需要谨记以下几点。
寻找出模式设计的合适粒度。
因此,这种应用程序版本的粒度太大。
Thus, the granularity of versioning here may become too large.
这一级别比俄罗斯娃娃级别有更多的粒度。
There is more granularity at this level than at the Russian Doll level.
那么,粒度大小重要吗?
这虽然合理,但是并没有更详细的颗粒度。
This is reasonable, but it doesn't allow more specific granularity.
我是怎样知道粒度的?
那如果我们需要更细的粒度呢?
在讨论操作参数时,同样要面对粒度的问题。
We again come to the question of granularity when we consider operation parameters.
阶段是一种非常粗粒度的组件。
授权和访问控制的粒度粗细不等。
Authorization and access control can vary from coarse - to fine-grained.
注意,授权条件可能需要更细的粒度。
Notice that conditions for requiring authorization are even more granular.
您常常会听到进行粗粒度建模的建议。
You will frequently hear the advice to model coarse-grained.
应用程序很像一个黑匣子,没有粒度可用于外部。
The application is much like a black box, with no granularity available outside it.
粒度是很重要的。
一般说来,您应该将数据放在最详细的粒度级别上。
As a general rule, you should keep data at the most detailed level of granularity.
两种方法的权衡实际就是易用性和控制粒度的权衡。
The key trade-off between the two methods is ease of use versus granularity of control.
第一个目标是实现完整的细粒度访问控制。
The first is to achieve complete and fine-grained access control.
这里也存在不同的粒度。
做出这样的区别仅仅是为了引入粒度这个重要的概念。
The distinction is made merely to introduce the important concept of granularity.
这里存在不同的粒度。
这些API本质上通常是非常细粒度的。
These APIs are usually very fine-grained and granular in nature.
从粗粒度的计划开始。
应用推荐