mirror of
https://github.com/SmallJoker/minetest-u_skinsdb.git
synced 2025-02-21 03:10:21 +01:00
7778dc5560
also trying to understand it. according to python: 1) you send a request 2) you MUST get response headers for (1) (THIS IS MANDATORY) 3) you send another request 4) you get response body for (2) 5) response headers for (3) 6) response body for (5) Only two requests can be pipelined. Surely this is an unavoidable, wait no it's just written into the code to error out if you don't do it that way. according to reality: 1) you send a request 2) you do not get response headers for (1) 3) you repeat steps 1-2 until enough responses are queued 4) you receive those responses as header,body,header,body... they even name it with a __ so to make it hard to override, but the state can safely go to Idle after a request has sent, whether or not response headers have come in. Sure the connection might close, but then you adjust to not pipeline, and re-send the rest of your requests over a new connection.
minetest-u_skins ================ An skin extention for the Minetest mod unified_inventory by Dean Montgomery It downloads the skins from the Minetest skin database. (http://minetest.fensta.bplaced.net) Requires latest unified_inventory from: https://github.com/minetest-technic/unified_inventory To download the latest skins you need to run: "./update_from_db.py" OR the win32.NET client Licenses: -------- cornernote: Lua source code (GPLv3) Fritigern: update_skins_db.sh (CC-BY-NC-SA 4.0) Krock: Lua source code (GPLv3) MT_skins_updater.exe (WTFPL) Credits: -------- RealyBadAngel unified_inventory and Zeg9 skinsdb