[
https://issues.apache.org/jira/browse/LUCENE-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966496#action_12966496
]
Robert Muir commented on LUCENE-2791:
-------------------------------------
{quote}
To my above comment and OVERLAPPED in my opinion not realy used (as not async):
Reading
http://msdn.microsoft.com/en-us/library/aa365467(VS.85).aspx#synchronization_and_file_position
it seems to behave little different when OVERLAPPED is non-null for
synchronous reads (as we do currently). But as you never read the contents og
OVERLAPPED after the function call, why pass it in? Please explain
{quote}
To position the read versus seeking the file. This is explained in the
documentation on that very same page!:
Considerations for working with *synchronous* file handles:
If lpOverlapped is not NULL, the read operation *starts at the offset that is
specified* in the OVERLAPPED structure and ReadFile does not return until the
read operation is complete. The system updates the OVERLAPPED offset before
ReadFile returns.
> WindowsDirectory
> ----------------
>
> Key: LUCENE-2791
> URL: https://issues.apache.org/jira/browse/LUCENE-2791
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Store
> Reporter: Robert Muir
> Attachments: LUCENE-2791.patch, LUCENE-2791.patch,
> WindowsDirectory.dll, WindowsDirectory_amd64.dll
>
>
> We can use Windows' overlapped IO to do pread() and avoid the performance
> problems of SimpleFS/NIOFSDir.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
