Hi Laslo, Do you really think the world needs another poll or select based web server?
The beauty of quark (as implied by its name) is the pure simplicity and hackability it may provide. What's wrong with fork()? Aren't processes and threads pretty much the same these days? What real problem do you intend to fix with running everything from the same process and introducing threads etc. when Unix fixed this problem 40 years ago already by introducing processes. Wasn't the idea behind quark to have a clear purpose, to easily maybe proxy or embed some scripts on top of http, to just serve some static content from a random directory for a limited time? Kind of the counterpart of curl, maybe allowing you to build a proxying tee for some debugging as apache/tomcat/etc. and other such monsters cannot easily be debugged anymore? Or in other words are we still on the right track? Isn't suckless all about sticking to the paradigms that have proven during time? If fork() ain't good enough, then fix the process model of your kernel instead ;) Thanks, Anselm