Overlapped I/O is a name used for asynchronous I/O in the Windows API. It was introduced as an extension to the API in Windows NT. Utilizing overlapped I/O requires passing an OVERLAPPED structure to API functions that normally block, including ReadFile, WriteFile, and Winsock's WSASend and WSARecv. The requested operation is initiated by a function call which returns immediately, and is completed by the OS in the background. The caller may optionally specify a Win32 event handle to be raised when the operation completes. Alternatively, a program may receive notification of an event via an I/O completion port, which is the preferred method of receiving notification when used in symmetric multiprocessing environments or when handling I/O on a large number of files or sockets. The th
| Attributes | Values |
|---|
| rdf:type
| |
| rdfs:label
| - Entrada/salida solapada (es)
- Overlapped I/O (en)
- 重叠I/O (zh)
|
| rdfs:comment
| - 重叠I/O（Overlapped I/O）是Windows操作系统对异步I/O的实现。自Windows NT引入. 重叠I/O对应于Unix的POSIX异步I/O的API (AIO). 重叠I/O特别适合于大量文件或者socket通信、pipe等场合. Windows 9x不支持重叠I/O. (zh)
- En informática, entrada/salida solapada (en inglés Overlapped I/O) es una extensión de entrada/salida (en adelante E/S) de la API de Windows que fue introducido en Windows NT. En la E/S síncrona, el proceso que realiza la petición entra en un estado de espera hasta que ésta ha finalizado. Un proceso que realiza una petición de E/S asíncrona, realiza una petición de E/S al núcleo. Si ésta es aceptada, el proceso continúa realizando otras tareas hasta que el núcleo le avisa de que la operación ha finalizado. En ese momento el proceso interrumpe la tarea que estaba realizando y procesa la información obtenida de la operación de E/S. (es)
- Overlapped I/O is a name used for asynchronous I/O in the Windows API. It was introduced as an extension to the API in Windows NT. Utilizing overlapped I/O requires passing an OVERLAPPED structure to API functions that normally block, including ReadFile, WriteFile, and Winsock's WSASend and WSARecv. The requested operation is initiated by a function call which returns immediately, and is completed by the OS in the background. The caller may optionally specify a Win32 event handle to be raised when the operation completes. Alternatively, a program may receive notification of an event via an I/O completion port, which is the preferred method of receiving notification when used in symmetric multiprocessing environments or when handling I/O on a large number of files or sockets. The th (en)
|
| dcterms:subject
| |
| Wikipage page ID
| |
| Wikipage revision ID
| |
| Link from a Wikipage to another Wikipage
| |
| Link from a Wikipage to an external page
| |
| sameAs
| |
| dbp:wikiPageUsesTemplate
| |
| has abstract
| - En informática, entrada/salida solapada (en inglés Overlapped I/O) es una extensión de entrada/salida (en adelante E/S) de la API de Windows que fue introducido en Windows NT. En la E/S síncrona, el proceso que realiza la petición entra en un estado de espera hasta que ésta ha finalizado. Un proceso que realiza una petición de E/S asíncrona, realiza una petición de E/S al núcleo. Si ésta es aceptada, el proceso continúa realizando otras tareas hasta que el núcleo le avisa de que la operación ha finalizado. En ese momento el proceso interrumpe la tarea que estaba realizando y procesa la información obtenida de la operación de E/S. En programación sobre Windows, la E/S solapada es una característica de la API de Windows para operaciones que tratan con ficheros. Se introdujo en Windows NT y es especialmente útil en aplicaciones que utilizan sockets y tuberías con nombre (named pipes). Windows 95, 98 y ME no soportan bien esta característica. Una posible analogía al concepto de E/S solapada en Unix serían los descriptores de fichero no bloqueantes (non-blocking file descriptors), pero implican una gran reestructuración del código para obtener resultados similares. Otra posibilidad sería la API para E/S asíncrona de POSIX (POSIX asynchronous I/O API) aunque no está soportada universalmente por todos los sistemas Unix. (es)
- Overlapped I/O is a name used for asynchronous I/O in the Windows API. It was introduced as an extension to the API in Windows NT. Utilizing overlapped I/O requires passing an OVERLAPPED structure to API functions that normally block, including ReadFile, WriteFile, and Winsock's WSASend and WSARecv. The requested operation is initiated by a function call which returns immediately, and is completed by the OS in the background. The caller may optionally specify a Win32 event handle to be raised when the operation completes. Alternatively, a program may receive notification of an event via an I/O completion port, which is the preferred method of receiving notification when used in symmetric multiprocessing environments or when handling I/O on a large number of files or sockets. The third and the last method to get the I/O completion notification with overlapped IO is to use ReadFileEx and WriteFileEx, which allow the User APC routine to be provided, which will be fired on the same thread on completion (User APC is the thing very similar to UNIX signal, with the main difference being that the signals are using signal numbers from the historically predefined enumeration, while the User APC can be any function declared as "void f(void* context)"). The so-called overlapped API presents some differences depending on the Windows version used. Asynchronous I/O is particularly useful for sockets and pipes. Unix and Linux implement the POSIX asynchronous I/O API (AIO). (en)
- 重叠I/O（Overlapped I/O）是Windows操作系统对异步I/O的实现。自Windows NT引入. 重叠I/O对应于Unix的POSIX异步I/O的API (AIO). 重叠I/O特别适合于大量文件或者socket通信、pipe等场合. Windows 9x不支持重叠I/O. (zh)
|
| prov:wasDerivedFrom
| |
| page length (characters) of wiki page
| |
| foaf:isPrimaryTopicOf
| |
| is Link from a Wikipage to another Wikipage
of | |
| is Wikipage redirect
of | |
| is foaf:primaryTopic
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)