3 ms·
If you don't care about speed, Berkeley sockets (bind, listen, accept, etc.) are just fine and very easy to deal with. If you do care about speed, you should b
by angersock 12y ago
If you don't care about speed, Berkeley sockets (bind, listen, accept, etc.) are just fine and very easy to deal with.
If you do care about speed, you should be banging against the operating system's provided tools anyways (IOCP on Windows, kqueue on BSD, epoll on Linux, etc.).
If it's abstraction you care about, you shouldn't be doing networking with raw TCP anyways, and should just use zmq, nanomsg, or whatever, and not drag in the entire clown car of boost.
- BinaryIdiot 12y ago> not drag in the entire clown car of boost. As far as I can tell you can just import what you want and not have to bring in the entire boost library to use asio. Is that not correct?
- VikingCoder 12y agoThis weekend I tried to bring in boost format. I tried to bring in JUST format, but nope... exceptions, and config, and a bunch of other stuff... Fifteen libraries, maybe?
- plorkyeran 12y agoasio specifically is available in a standalone version that does not depend on any other boost libraries.
- zwily 12y agoBoost's asio has backends (reactors) for IOCP, kqueue, etc. The whole point is you write to one interface and take advantage of their performance.