3 ms·
Not super fair to say linux sockets (in the README) and I/O in the title when it's really just a TCP client - you force SOCK_STREAM and bind(2).
by ac_slater 9y ago
Not super fair to say linux sockets (in the README) and I/O in the title when it's really just a TCP client - you force SOCK_STREAM and bind(2).
- matt42 9y agoThis is default behaviour but you can fill you own socket file descriptor if you want, using the second overload of moustique_listen: template <typename G, typename H> int moustique_listen(int listen_fd, G closed_connection_handler, H data_handler);
- matt42 9y agoBut you're right, maybe we want two moustique_listen_tcp moustique_listen_udp helpers. I put this in my todolist.
- primitur 9y agoWhile you're at it please add a namespace .. it'd make it a lot easier to administer in a project. Great project by the way - I've put it on my workbench-TODO for a little hacking some time in the next few days. I've got a standard 'command processing server' project that I've been hacking on over the years, I might try to hack up a moustique_ integration, just for grins.