I've also found the question on SO, I'll give it a shot later today.
On Aug 20, 2012, at 10:18 AM, Michael Herndon mhern...@wickedsoftware.net
wrote:
I went to update the twitter feed and saw these questions in case
anyone wants to answer these:
@Nick_Craver
@LuceneDotNet - is anyone
Chris,
All you have to do is create a new AppDomain properly and marshal the
call into that app domain.
You'll need a wrapper that derives from MarshalByRefObject so the call
is marshaled; it's in the marshaled call that you do your test work and then
marshal the results for
Prescott,
You really don't need to do that; reads and writes of reference fields are
guaranteed to be atomic as per section 5.5 of the C# Language Specufication
(Atomicity of variable references)
If you were doing other operations beyond the read and write that you wanted to
be atomic, then
I've cast my vote already, but +1 to Wyatt's expression
-Original Message-
From: Wyatt Barnett [mailto:wyatt.barn...@gmail.com]
Sent: Tuesday, May 10, 2011 12:46 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache
Lucene.Net
+1
-Original Message-
From: Troy Howard [mailto:thowar...@gmail.com]
Sent: Monday, May 09, 2011 4:05 PM
To: lucene-net-dev@lucene.apache.org; lucene-net-u...@lucene.apache.org
Subject: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache Lucene.Net
2.9.4
All,
Please cast your
-for-line
port code, so best to keep it in SupportClass.
- Nicholas Paldino [.NET/C# MVP]
-Original Message-
From: Richard Wilde [mailto:rich...@wildesoft.net]
Sent: Sunday, May 01, 2011 6:01 AM
To: lucene-net-...@incubator.apache.org
Subject: [Lucene.Net] Medium trust security
As a consumer (and I think that most consumers would agree), I'd have to
disagree STRONGLY on trading off performance for ease of conversion.
Lucene and Lucene.NET is predicated on performance, compromising that, IMO,
runs contrary to the core principals of Lucene.
- Nick
-Original
Erik,
It's the fact that the API is exactly the same (as well as the lines
of code, practically) which causes many of the issues in Lucene.NET (not
only in use but in implementation), as while Java and C# are very similar,
that doesn't guarantee the same results.
But that's an
