Here `conn` is net.socket instance, so it should be called as one.
Otherwise request is very likely to end up with crash and PANIC.
nwf edited in light of bcb669a4a0a49e857186093eb79b6f27a3158ad7
* Add missing globals from luacheck config
* Fix luacheck warnings in all lua files
* Re-enable luacheck in Travis
* Speed up Travis by using preinstalled LuaRocks
* Fix more luacheck warnings in httpserver lua module
* Fix DCC module and add appropriate definitions to luacheck config.
* Change inline comments from ignoring block to only ignore specific line
* Add Luacheck for Windows and enable it for both Windows and Linux
* Change luacheck exceptions and fix errors from 1st round of polishing
* Add retry and timeout params to wget
* lua_modules/fifo: a generic queue & socket wrapper
One occasionally wants a generic fifo, so here's a plausible
implementation that's reasonably flexible in its usage.
One possible consumer of this is a variant of TerryE's two-level fifo
trick currently in the telnetd example. Factor that out to fifosock for
more general use.
* lua_examples/telnet: use factored out fifosock
* lua_modules/http: improve implementation
Switch to fifosock for in-order sending and waiting for everything to be
sent before closing.
Fix header callback by moving the invocation of the handler higher
* fifosock: optimistically cork and delay tx
If we just pushed a little bit of data into a fifosock that had idled,
wait a tick (1 ms) before transmitting. Hopefully, this means that
we let the rest of the system push more data in before we send the first
packet. But in a high-throughput situation, where we are streaming data
without idling the fifo, there won't be any additional delay and we'll
coalesce during operation as usual.
The fifosocktest mocks up enough of tmr for this to run, but assumes
an arbitrarily slow processor. ;)
