Lua mongoose bindings for rapid develpment

[TheRootED24]

I am nearing completion of the lua bindings for the entire mongoose api. I have replicated most of the examples from the documentation and tutorials in lua . One of the main goals for this library is to represent the actual c code as closely as possible, to allow easy translation from lua to an actual C program. I am quite happy with the results so far, i feel it feels very close to the actual C api.

for example, compare the example from the respective github repos

Mongoose C

  #include "mongoose.h"   // To build, run: cc main.c mongoose.c

// HTTP server event handler function
void ev_handler(struct mg_connection *c, int ev, void *ev_data) {
  if (ev == MG_EV_HTTP_MSG) {
    struct mg_http_message *hm = (struct mg_http_message *) ev_data;
    struct mg_http_serve_opts opts = { .root_dir = "./web_root/" };
    mg_http_serve_dir(c, hm, &opts);
  }
}

int main(void) {
  struct mg_mgr mgr;  // Declare event manager
  mg_mgr_init(&mgr);  // Initialize event manager
  mg_http_listen(&mgr, "http://0.0.0.0:8000", ev_handler, NULL);  // Setup listener
  for (;;) {          // Run an infinite event loop
    mg_mgr_poll(&mgr, 1000);
  }
  return 0;
}

Lua script

local mg = require "mg_lua"   -- include the mg_lua library 

local web_root = ".";
-- HTTP server event handler function
function ev_handler(c, ev, ev_data) 
  if (ev == MG_EV_HTTP_MSG) then
    local hm = mg.http.message.new(ev_data);
    local opts = mg.http.serve_opts.new(web_root);
    mg.http.serve_dir(c, hm, opts);
  end
end

local function main(...) 
  local run = true
  local mgr = mg.mgr.new();  -- Declare event manager
  mg.mgr.init(mgr);  -- Initialise event manager
  mg.http.listen(mgr, "http://0.0.0.0:8000", "ev_handler");  -- Setup listener
  while(run) do         -- Run an infinite event loop
    mg.mgr.poll(mgr, 1000);
  end
  return 0;
end

I have tested 80-90% of the api and as mentioned, replicated most of the tutorials found on the documentation page and in from the github tutorials.

the project can be found on github --> https://github.com/TheRootED24/mg_lua

all criticisms all welcome. Cheers

[shakfu]

Cool project.. Incidentally, I saw that threads.so is checked in to your repo. I'm assuming that's not deliberate?

[TheRootED24]

the threads.so is used in the multi-threading example .. but the binary should not be included, good catch. I will add it as an optional dependency for the multi-threading example.

cheers

[scaprile]

Please keep your discussion in your repo, this is to tell us about a cool way to use Mongoose with your project, not the opposite. Thank you

[shakfu]

@scaprile

Please keep your discussion in your repo, this is to tell us about a cool way to use Mongoose with your project, not the opposite. Thank you

If the project is a binding of mongoose for another language, as is the case here, are you suggesting that discussing it in the mongoose discussion group is not appropriate?

[scaprile]

IMHO, you are not discussing Mongoose but the innards of your implementation in a particular language.
We love to see you writing bindings for programming languages, and it is great to see an example on how to use it. The internals of that, not related to Mongoose itself at all, IMHO, do not belong here.
How to do it, binding internals, IMHO, do not belong here, those are (e.g.) Lua details, not Mongoose details.
We do not use Lua and are not able to test it, and I'd have to submit for review and approval, but we could even add an example to the tutorials section. Feel free to submit all these, feel free to discuss usage gotchas, but please do not discuss implementation internals here.
We maintainers receive a notification for every message, we thrive to respond asap to our customers and users, we just ask to keep the noise down.

[shakfu]

IMHO, you are not discussing Mongoose but the innards of your implementation in a particular language. We love to see you writing bindings for programming languages, and it is great to see an example on how to use it. The internals of that, not related to Mongoose itself at all, IMHO, do not belong here.. We maintainers receive a notification for every message, we thrive to respond asap to our customers and users, we just ask to keep the noise down.

Fair enough, @scaprile we will follow your guidelines.