Michael,
From my perspective, this is a memory-mapped file. Explicit support
for memory-mapped files is provided in .NET 4.0, but from what I can tell (I
just joined the mailing list today), that's a long way off.
However, you can provide the same functionality through the Win32
API (which can be accessed through the P/Invoke layer). Here are the
functions:
http://msdn.microsoft.com/en-us/library/aa911527.aspx
Note if you want to create an implementation of this, you are going
to have to use SafeHandle instances. If you have to create specialized
ones, doing it right requires some pretty delicate work (you need to
attribute everything correctly for CER guarantees).
- Nick
-----Original Message-----
From: Michael Garski [mailto:[email protected]]
Sent: Monday, November 09, 2009 7:16 PM
To: [email protected]
Subject: Lucene.Net.Store Namespace
Woo-hoo! I've been authorized to commit full-time to getting Lucene 2.9
in shape and ready to go!
I've submitted 6 patches for various fixes in the Store namespace, they
are all independent, however there may be some cleanup throughout the
namespace once they are all reviewed, approved, and committed. There
are certainly some optimizations that can be done in there and I plan on
taking those on when the tests are all in a passing state.
I suggest we hold off on a .NET equivalent to NIOFSDirectory at this
time. I'm not even sure if there even is a .NET or underlying system
call that provides the same functionality as the FileChannel classes.
Anyone have any info on that topic?
Michael
Michael Garski
Sr. Search Architect
310.969.7435 (office)
310.251.6355 (mobile)
www.myspace.com/michaelgarski
smime.p7s
Description: S/MIME cryptographic signature
