Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 4
    At a high level, major web servers come with a lot of functionality you need to totally rebuild, that you can otherwise configure or simply ignore, if you "self-host." Simple things, like serving up static files, and configuring Expires and ETag headers. And then more complicated things, like separating traffic by host, keeping applications away from each other's memory, SSL, and managing thousands of concurrent requests ... Commented Sep 21, 2016 at 17:10
  • You could just write your own HTTP service using C++ sockets. Commented Sep 21, 2016 at 17:28
  • 1
    dotnetfunda.com/interviews/exclusive/show/755/… Commented Sep 21, 2016 at 17:33
  • 1
    Many .net applications call themselves "self hosted" while they still use http.sys, which is rather misleading IMO. Commented Sep 21, 2016 at 18:23
  • In my view, it's merely a historical consequence of the evolution of the use cases for the TCP/HTTP protocols and services stack. E.g., in the case of HTTP, the daemon or service used to be sitting on top of the OS as a sort of central hub of anything-web content, to which other local or remote applications would delegate the consumption or offering of hypertext/hypermedia content. Commented Sep 29, 2016 at 23:12