服务器会返回一个文件句柄和状态信息。
使文件句柄可由子进程继承。
服务返回一个文件句柄，正如在清单12中所看到的。
The service returns a file handle, as you can see in Listing 12.
READ包含文件句柄、状态、偏移、和读取计数。
The READ consists of the file handle, state, offset, and count for the read.
需要创建文件句柄，才能在ZIP文件结构中识别文件。
You need to create a file handle to identify it in the ZIP file structure.
此外，还检索每个文件的映射，并保存到到其文件句柄中。
Furthermore, it retrieves and retains the mappings for every file to its file handle.
同时，强制卸载会导致所有目标卷上打开的文件句柄失效。
At the same time, a forced dismount invalidates all open handles to files on the target volume.
性能下降问题，诸如释放资源（包括文件句柄、连接、信号和流）失败。
Performance Degradations such as failure to correctly release resources including file handles, connections, semaphores, and streams
在与POSIX兼容的系统上，文件句柄是进程属性，而不是线程属性。
On POSIX-compliant systems, file handles are process and not thread attributes. Here are a few guidelines for using file locking.
现在，把新的JPEG文件句柄交给curl，结果几乎与我所期望的一样。
Now, handing curl the new JPEG file handle produces exactly the results I want-almost.
服务器提供了一个root文件句柄，对应于服务器导出的文件系统树的顶。
The server provides a root file handle that represents the top of the file system tree exported by the server.
这些设施包括打开文件句柄(文件描述符)、共享内存、进程同步原语和当前目录。
Facilities include open file handles (file descriptors), Shared memory, process synchronization primitives, and current directory.
关闭原始文件句柄时，互斥体句柄已关闭，并且对数据损坏保护会丢失。
When the original file handle is closed, the mutex handle is closed and the protections against data corruption are lost.
使用这两种文件句柄类型，服务器实现可以具备与服务器上操作系统的文件系统相匹敌的能力。
With these two file handle types, the server implementation can match the abilities of the file system at the server along with the operating system.
当应用程序打开一个文件句柄读取文件以处理文档时，它通常读取文件后就不再需要文件句柄了。
When an application opens a file handle to read in so it can process a document, it typically reads from the file and then has no further need for the file handle.
应用程序可以拥有堆栈、共用内存、文件句柄、消息队列这样的事物，而DLL不能。
An application can own things such as a stack, global memory, file handles, and a message queue, but a DLL cannot.
文件句柄被映射到文件标识符，显示在application-instance.xml 中。
The file handle is mapped to the file identifier and exposed in the application-instance.xml.
但是，这样做将降低你的搜索速度。同时，你有可能会用光你的文件句柄如果你把合并因子设置的太大。
However, this will slow down searching, and, you will run out of file descriptors if you make it too large.
基于以上成功的GETATTRs和LOOKUPs，客户端创建文件句柄，为用户的未来需求而提供的。
Based upon successful GETATTRs and LOOKUPs, the client creates a file handle that is provided to the user for future requests.
最常用的非托管资源类型是包装操作系统资源的对象，例如，文件句柄、窗口句柄或网络连接。
The most common type of unmanaged resource is an object that wraps an operating system resource, such as a file handle, window handle, or network connection.
在这里，布局枚举持有文件片段的服务器、每个服务器上文件片段的大小，以及每个片段的NFS文件句柄。
Here, the layout enumerates the servers that hold the pieces of the file, the size of the stripe on each server, and the NFS file handle of each segment.
更好的办法是让t wisted服务器自己拥有一个针对日志文件的文件句柄，只在需要时才读取新记录。
A better approach is to let the Twisted server itself hold a file handle for the log file, and only read new records when needed.
一个很好的例子是文件处理，你需要获取一个文件句柄，从文件中读取数据，然后关闭文件句柄。
A very good example for this is the situation where you want to gain a handler to a file, read data from the file and the close the file handler.
但它确实能够让人神往，例如，通过写／读文件句柄，可以直接写／读数据库，或者在关闭文件时发送一封电子邮件。
They do offer fascinating possibilities, for instance writing/reading a file handle could write/read directly to a database, or send an e-mail when you close the file.
对于多个文件句柄来说，就可以把这些多个文件句柄合并成一个单独的对象，这个可以被用来结合同步点？
This can be used to combine the synchronization point for multiple file handles into a single object.
在NSFNoteCopyAndEncryptExt2 方法中使用取到的ID文件句柄，用以对文档加密。
Use the ID file handle in the NSFNoteCopyAndEncryptExt2 method to encrypt the document.
CreateIoCompletionPort函数会使一个I/O完成端口与一个或多个文件句柄发生关联。
The CreateIoCompletionPort function associates an I/O completion port with one or more file handles.
如果说平台库提供终结器来清除打开的文件句柄，这大大降低了忘记显式地关闭这些句柄的风险，为什么不更多地使用终结器呢？
If the platform libraries provide finalizers for cleaning up open file handlers, which greatly reduces the risk of forgetting to close them explicitly, why aren't finalizers used more often?
如果说平台库提供终结器来清除打开的文件句柄，这大大降低了忘记显式地关闭这些句柄的风险，为什么不更多地使用终结器呢？
If the platform libraries provide finalizers for cleaning up open file handlers, which greatly reduces the risk of forgetting to close them explicitly, why aren't finalizers used more often?
应用推荐