6 ms·

Thanks! I understand your point, but a fork server is so simple I don't think there is much that can go wrong there, if it was serving more data I would be wo

Thanks! I understand your point, but a fork server is so simple I don't think there is much that can go wrong there, if it was serving more data I would be worried, but its meant to do a quick and short reply.

konad 16y ago
it's not called a forkbomb for nothing
- BuckToBid 16y ago
  http://en.wikipedia.org/wiki/Fork_bomb http://en.wikipedia.org/wiki/Fork_bomb Fork Bombs are easier to pull off from the command line. Not so much with DOS. I would say that loading a large webserver for each request would use up more resources than a tiny C program. Thats the whole point of the post.
  - konad 16y ago
    You're right about the webserver being overload. Threads would be less expensive than processes. I would use Go for this service myself. Defending against abuse is hard whichever way one goes.
rubashov 16y ago
Writing your own server in C seems a little crazy anymore. Just use a C++ framework like POCO or ASIO. POCO gives you a fast httpserver component with all the tricky stuff figured out.