Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I don't understand why you're using fork. Since there's no a whole lot of logic to DHCP, it's not like you have large tasks you need to fork off to keep your server available. Don't you just need to hit a hash and send a reply? That should be quick enough to just handle as it comes without splitting off another process. Similarly, if you *want* to use fork, then I don't understand why you want to use AnyEvent. I've not used AnyEvent before, so there might simply be something I don't understand, though. ...roboticus When your only tool is a hammer, all problems look like your thumb. In reply to Re: anyevent + fork = problem
by roboticus
|
|