lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2791) WindowsDirectory
Date Fri, 03 Dec 2010 11:53:10 GMT


Robert Muir commented on LUCENE-2791:

To my above comment and OVERLAPPED in my opinion not realy used (as not async):
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 

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:
>             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

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:
For additional commands, e-mail:

View raw message