3 ms·
> "Write programs that do one thing and do it well." So why does this WebSocket daemon also serve static files and CGI applications?
by cypher543 12y ago
> "Write programs that do one thing and do it well."
So why does this WebSocket daemon also serve static files and CGI applications?
- spoiler 12y agoBecause you need to implement a tiny HTTP server for WebSockets anyway (if you want't them to work from browsers). So, adding the ability to serve static files on top of that is trivial. Not sure why they added CGI, though.
- joewalnes 12y agoThat indeed was a dilemma. Although it focusses on doing one thing well, there were also a few core things that are useful to support a websocket based app - namely a place to serve the actual web content from (static) and the ability to use websocketd using vanilla http instead of websockets (cgi).