MirrorSave
/
nodemcu-firmware
mirror of https://github.com/nodemcu/nodemcu-firmware.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
nodemcu-firmware/lua_modules/http/http-example.lua

38 lines
1.3 KiB
Lua
Raw Normal View History

http module draft, with example
2015-01-19 18:12:06 +01:00
------------------------------------------------------------------------------
-- HTTP server Hello world example
--
-- LICENCE: http://opensource.org/licenses/MIT
-- Vladimir Dronnikov <dronnikov@gmail.com>
------------------------------------------------------------------------------
Rename http server Lua module and fix its documentation (#2594)
2018-12-19 12:23:14 +01:00
require("httpserver").createServer(80, function(req, res)
http module draft, with example
2015-01-19 18:12:06 +01:00
-- analyse method and url
cleanup http module
2015-01-19 21:32:16 +01:00
print("+R", req.method, req.url, node.heap())
http module draft, with example
2015-01-19 18:12:06 +01:00
-- setup handler of headers, if any
req.onheader = function(self, name, value)
A generic fifo and fifosock wrapper, under telnet and http server (#2650) * 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. ;)
2019-02-16 13:51:40 +01:00
print("+H", name, value)
http module draft, with example
2015-01-19 18:12:06 +01:00
-- E.g. look for "content-type" header,
-- setup body parser to particular format
-- if name == "content-type" then
-- if value == "application/json" then
-- req.ondata = function(self, chunk) ... end
-- elseif value == "application/x-www-form-urlencoded" then
-- req.ondata = function(self, chunk) ... end
-- end
-- end
end
-- setup handler of body, if any
req.ondata = function(self, chunk)
print("+B", chunk and #chunk, node.heap())
if not chunk then
-- reply
res:send(nil, 200)
res:send_header("Connection", "close")
A generic fifo and fifosock wrapper, under telnet and http server (#2650) * 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. ;)
2019-02-16 13:51:40 +01:00
res:send("Hello, world!\n")
http module draft, with example
2015-01-19 18:12:06 +01:00
res:finish()
end
end
-- or just do something not waiting till body (if any) comes
--res:finish("Hello, world!")
cleanup http module
2015-01-19 21:32:16 +01:00
--res:finish("Salut, monde!")
http module draft, with example
2015-01-19 18:12:06 +01:00
end)