Although you're kidding, there was an embedded server that reduced CPU/memory use by working almost exclusively in TCP. It evdn pre-encoded HTML pages as TCP packets that ig transmitted.
“Supporting language X” isn't the same as “can be called from language X if you manually use the FFI”. At the very least, the bindings should come out of the box.
7 comments
[ 5.7 ms ] story [ 34.4 ms ] threadDoes it support TCP language?
The Python module does not require one to use an FFI: https://github.com/ers35/modserver/blob/master/src/example/p...
More idiomatic wrappers can be written later, but the FFI based bindings have to come first.
I updated the readme to make this more clear.
Of course. But FFI bindings alone don't count as “support”.
> More idiomatic wrappers can be written later
Then “support for <language X>” is “planned” or “work in progress”.