MacHTTP-js vs. Node.js vs. django-mysql vs. kWS Comparison Chart

As an asynchronous event-driven JavaScript runtime, Node.js is designed to build scalable network applications. Upon each connection, the callback is fired, but if there is no work to be done, Node.js will sleep. This is in contrast to today's more common concurrency model, in which OS threads are employed. Thread-based networking is relatively inefficient and very difficult to use. Furthermore, users of Node.js are free from worries of dead-locking the process, since there are no locks. Almost no function in Node.js directly performs I/O, so the process never blocks except when the I/O is performed using synchronous methods of Node.js standard library. Because nothing blocks, scalable systems are very reasonable to develop in Node.js. Node.js is similar in design to, and influenced by, systems like Ruby's Event Machine and Python's Twisted. Node.js takes the event model a bit further. It presents an event loop as a runtime construct instead of as a library.

kWS is a lightweight and fast Web Server especially designed for Android mobile devices. It can be used to host websites and to serve files over HTTP. kWS implements HTTP-1.0. Basic & digest authentication for secure access. Server side includes (SSI). Directory index, directory downloads in tar, tgz & zip formats. Resumable file downloads, built-in Dynamic DNS updates, up to 20 parallel connections, comprehensive HTTP logs. HTTPS/TLS support with BKS & PKCS12 keystores. Password-based file encryption (128 bit AES & Triple DES). GZip file compression, directory index in JSON & XML formats and index sorting, highly configurable with support for up to 999 per-port parallel connections. Directory level configuration, support for more Dynamic DNS providers like ZoneEdit etc. kWS also provides auto start on boot.