How to efficiently serve static files in .NET?

Question

I have searched for solution, and what I found out so far:

Hosting static content directly using nginx or iis. They are built to serve static files efficiently.
For NancyFx there is a StaticContentConventionBuilder
For OWIN app there is a StaticFileMiddleware
Custom static handler: stream file from file system per each request (with old etag) and manually handle etags, last-modified and cache-control headers.

Because of my constraints I can't ~~(or don't want to)~~ use 1-3 options.

I think option 4 is not good one (please, correct me, if I'm wrong) because it's expensive to operate with file system. So I want to reinvent the wheel and create efficient static content handler (with caching files content in memory, file system watching etc) or find other solutions.

I looked over docs and source code of managing static content in NancyFx and StaticFiles in OWIN. Both actually are similar to option 4. Why are these methods considered to be efficient?

How to efficiently (customly) serve static files in .NET?

it is confusing when you say you can't use iis. asp.net is hosted within iis, and the file extension dictates which engine the page is served, so if you have a .htm file, then iis won't pass it on to the asp.net engine to process. voila! — Jeremy, Mar 01 '17 at 19:25
does this help? http://stackoverflow.com/questions/28476795/how-to-serve-index-html-with-web-api-selfhosted-with-owin — Jeremy, Mar 01 '17 at 21:16
*Why are these methods considered to be efficient?* - why do you consider them to be inefficient? — tom redfern, Mar 02 '17 at 10:07
@tomredfern because it's expensive to operate with file system for each request — kanggary, Mar 02 '17 at 11:59
@Jeremy thank you for link. that answer actually is about option #3. — kanggary, Mar 02 '17 at 12:01
@tomredfern _efficient_ - accomplishing something with little waste. I am sorry, my english is not good enough — kanggary, Mar 02 '17 at 12:10

How to efficiently serve static files in .NET?

0 Answers0