Re: Approaches to concurrency

Replies are listed 'Best First'.
Re^2: Approaches to concurrency by BrowserUk (Patriarch) on Feb 09, 2009 at 15:50 UTC
...and is slower, more cpu intensive, more memory hungry and threads. Shared variables are "achieved" by serialising them with Storable and transmitting them to all the other ~~threads</strike</> processes via sockets.~~ ~~That's like putting a single lane chicane on a multi-lane highway. Necessary occasionally, but totally defeating the purpose of having multiple lanes.~~ 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. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^3: Approaches to concurrency by rhesa (Vicar) on Feb 09, 2009 at 16:01 UTC
But it'd work on non-threaded perls, and that's the use case for it. It certainly wouldn't make sense to replace actual threads with forks, especially on windows :)	[reply]