![mono framework asp.net mono framework asp.net](https://static.wixstatic.com/media/81e00d_6f9e237e12af463d8bae437b7e55ed0b~mv2.jpg)
It would be also useful to have a basic understanding of webservices and how they are implement in. To read this article you need to have a basic knowledge on how web servers and in particular IIS handles request. My implementation includes this but also opens different implementation scenarios that are not possible under the mono implementation.
![mono framework asp.net mono framework asp.net](https://en.opensuse.org/images/c/c9/Mono-stacks.png)
The ultimate goal of the Mono implementation is to have a fastcgi replacement to host ASP.NET. Also if you want to use it you will need to deploy the Mono libraries as long as it depends on them to work. If you'll have a chance to look at the source code, you will find that it's really overcomplicated. You can find an implementation of the fastcgi protocol on Mono.
![mono framework asp.net mono framework asp.net](https://i.stack.imgur.com/2rWKn.png)
#Mono framework asp.net windows
With this implementation is also possible to host an ASP.NET application (also MVC) with a Nginx webserver on both Windows and Linux. The purpose of this implementation is to have a more reliable solution than the one offered with Mono and also a more cleaner and reusable implementation of the protocol to host not only ASP.NET applications but also custom low level (and fast) applications, the ones that usually are implemented with an HttpListener. In this article I'm going to present the first version of my open source implementation of the fastcgi protocol under.