in reply to Non-forked, bi-directional client/server
- Always give multi-threading a try whenever you are thinking of fork.
I am not saying you should never use fork, but look back at the history, one big reason that fork was/(unfortunately is) heavily used is that Perl did not support multi-thread (very well), which is getting improved from revision to revision.
Breaking the old norms, and re-establish our norms on the new ground, especially for Perl newbies do not have a burden of history.
Always look at both fork and multi-thread, make your decision on a case by case base.
- The other thing is that, taking fork and multi-thread as helper, not restriction. It is obvious that, you can archive what you want to do here without multi-thread or fork.
Neither is it said that fork or multi-thread is a must, nor is it said that multi-thread or fork is the best. Look at the benefits that multi-thread and fork may give you, and make your design decision. Don't use those techniques, just because they are cool, and don't refuse to use them, just because they are a little bit more complex.