Proper structuring of Lucene.Net usage in an ASP.NET MVC site

Question

I\'m building an ASP.NET MVC site where I plan to use Lucene.Net. I\'ve envisioned a way to structure the usage of Lucene, but not sure whether my planned architecture is OK

Answer 1

I would probably skip the caching -- Lucene is very, very efficent. Perhaps so efficent that it is faster to search again than cache.

The OnApplication_Start full index feels a bit off to me -- should probably be run in it's own thread so as not to block other expensive startup activities.