反之，如果您禁用了深度缓冲，那么必须在绘制3d对象的顺序上付出一定精力。
Conversely, if you disable the depth buffer, you have to pay attention to the order in which you draw your 3d objects.
由于不同的内部存储模型和潜在的巨大对象(大到2gb)，这里没有缓冲池。
Due to the different internal storage model and the potentially huge objects (up to 2gb), no buffer pool is involved here.
通过使用深度缓冲，对象可得到正确的渲染。
为了在不同缓冲池中隔离对象，您可以在同一个数据库中创建一个以上的表空间，并给每一个表空间关联不同的缓冲池。
To isolate objects in different buffer pools, you can create more than one table space in the same database, and associate each table space with separate buffer pools.
workrequestqueuesize参数指定工作请求队列的大小，这是一个容纳计划内工作对象的缓冲。
The work request queue size parameter specifies the size of the work request queue, a buffer that holds scheduled work objects.
但WorkingCopy并没有任何子对象，——它只是一个未被保存且未被结构化的文本的缓冲区。
But the WorkingCopy doesn't have any children, yet — it's just a buffer of unsaved, unstructured text.
首先必须分配用户空间数据缓冲区和检测缓冲区，并将它们指向sg_io_hdr对象。
First the user space data buffer and sense buffer should be allocated and made to point to the sg_io_hdr object.
在过去，您也许曾经试图利用JMSConnection对象的多线程本性，并将它们缓冲到EJB组件或者servlet的静态变量中。
In the past, you may have been tempted to take advantage of the multithreaded nature of JMS Connection objects and cache them in a static variable of an EJB component or servlet.
用AXIOM的术语称为缓冲：无论是否在内存中建立了对象模型，AXIOM都允许获得StAX事件或者序列化XML。
The AXIOM terminology for this is caching: AXIOM allows you to get StAX events or serialize the XML with or without building the object model in memory.
具体地说，管理员必须定义适当的数据库对象，比如分区组、表空间、缓冲区池等等。
Specifically, an administrator must define appropriate database objects, such as partition groups, table Spaces, buffer pools, and so on.
如果调用一个对象的方法，代码也被添加到内部缓冲区中。
If you call an object's method, the code is added to the internal buffer.
对象是从线程本地分配缓冲区中直接分配的，线程本地分配缓冲区是线程先前从堆中分配的。
Objects are allocated directly from a thread local allocation buffer that the thread has previously allocated from the heap.
当数组用于实现诸如堆栈或环形缓冲区之类的数据结构时，会出现另一种形式的对象游离。
Another form of object loitering arises when arrays are used to implement data structures such as stacks or circular buffers.
需要实例化历史堆栈对象并从缓冲区加载它们。
The history stack object will need to be instantiated and loaded from cache.
您可能觉得用同一个缓冲区打开两个FILE对象会有风险。
You might think it seems a little risky to open two FILE objects using the same buffer.
数据服务器层是数据网格的组成部分，通过在内存中缓存对象来缓冲数据库访问，以实现更高的性能。
Data Server tier, part of data Grid, buffers database access by caching objects in-memory for higher performance.
此对象根据对象的性质确定要解析的语言并从 WorkingCopy 的文本中构建一个字符缓冲区。
This object determines the language being parsed from the project's nature and builds a character buffer from the WorkingCopy's text.
进行缓冲之后，out put .write方法将文件数据写入到outputStream对象的套接字中。
Once buffered, the file data is written through the output.write method into the socket of the OutputStream object.
但是结果是，缓冲区永远不会被释放，因为它对程序来说总是可及的(除非leakychecksum对象被垃圾收集了)。
But as a result, the buffer is never released because it is always reachable by the program (unless the LeakyChecksum object is garbage collected).
所有的输入在缓冲的同时所有的输出都将被清空，每一个对象都有自己的输入缓冲。
All output is flushed while all input is buffered. Each object contains its own input buffer.
fmemopen()函数提供了一个stdioFILE *对象，该对象表示内存中的一个缓冲区。
The fmemopen() function gives you a stdio FILE * object that refers to a buffer in memory. Replacing the open of test.jpg with a single call to fmemopen solves half the problem
当然，但是您将很快看见，在2.4.4，字节缓冲区对象拥有一大堆方便的方法，作为别的基本数据类型用来获取和存放缓冲区内容。
Sure, but as you'll soon see in Section 2.4.4, ByteBuffer objects possess a host of convenience methods for getting and putting the buffer content as other primitive data types.
所以利用正交投影和放置你的对象层在不同深度可以生成数据有用的递延照明深度缓冲区。
So by using a orthoprojection and placing your objects on layers at various depth you can generate a depth buffer with data usefull for deferred lighting.
缓冲区收到TOKEN_OWNER结构，其中包含默认的所有者安全标识符项(SID)为新创建的对象。
The buffer receives a TOKEN_OWNER structure that contains the default owner security identifier (SID) for newly created objects.
当对象以流的情势到（来自）一个对象办事器，它们直接从办事器活动到（来自）用户—办事器并不缓冲它们。
When objects are streamed to or an object server, they are streamed directly through the proxy server to or the user – the proxy server does not spool them.
在复杂对象的缓冲技术方面，提出并实现了对每一个复杂对象维持一个非定长页面的对象缓冲区的方法，避开了传统定长负面缓冲机制的缺陷。
Presents the implementation technique of keeping a non-fixed-page object buffer for each complex object, which avoids the drawback of the traditional fixed-page buffering mechanism.
实现了图形对象的拓扑分析、叠置分析和缓冲区分析等空间分析功能。
The spatial analysis, including topological analysis, overlay analysis, buffer analysis and so on, is achieved.
在QOS提供程序特定缓冲区中发现一个无效的波形丢弃模式对象。
An invalid shape discard mode object was found in the QOS provider specific buffer.
这会潜在地在每个I/O导致缓冲区拷贝和对象粗制滥造，这确实是我们喜欢避免的五花八门的事情。但，依赖于实现，事情或许没这么糟糕。
This can potentially result in buffer copying and object churn on every I/O, which are exactly the sorts of things we'd like to avoid.
针对三维可视化的特点，本文分析了该集成机制的性能优化方法，并讨论了基于三维对象的动态缓冲管理技术。
According to characteristics of 3d visualization, we analyze some methods for optimal performance and discuss dynamic buffer management technique on 3d object.
应用推荐