Unix Domain Socked, Named Pipes and HTTPS

[arthurafarias]

Hello, I would like to contribute to this project by adding support to unix domain socket, named pipes and https. It is something in the architecture that I would like to suggest. Instead of using ip address and port to listen, I would like to suggest using an url like http://localhost:4000, https://localhost:4000 or file://./path-to-unix-domain-socket-or-windows-named-pipe.

I am currently working on that feature. If you could check and give me some suggestions I would appreciate.

https://github.com/arthurafarias/hexo-server/commit/e903795e9d3516fea5a185ef4e6925de559d8dc1

[NoahDragon]

I feel it is good feature, but don't know when it applies?

[arthurafarias]

When you need deploy this application behind NGINX, IPC is faster than deploying a virtual network and binding the service to it. By example in my server I created several services that uses different technologies. The only way to use them toguether in the same port is by proxying them.