Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re: socket server threads or fork

by BrowserUk (Pope)
on Jun 18, 2013 at 17:40 UTC ( #1039611=note: print w/ replies, xml ) Need Help??


in reply to socket server threads or fork

I think the best option is use fork for starting new process by each connection because what I need is performance and I don't need to share info between the established connections.

If you are on *nix, use fork; if you are on Windows, use threads. If you need to run anywhere perl does, use the latter.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.


Comment on Re: socket server threads or fork

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1039611]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (6)
As of 2015-07-06 03:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (69 votes), past polls