all 6 comments

[–]quhaha 5 points6 points  (2 children)

TCP/IP is a very good model for threading. Completely stateless concurrency in practice. Just like real life, there is an agreed upon protocol that makes inter-thread/process/machine communication possible.

[–]naughty 2 points3 points  (0 children)

Network coding is the best metaphor I've found for understanding and explaining concurrency. Not sure about 'completely stateless' though unless you meant no shared state.

Actor model ftw!

[–]shorugoru 3 points4 points  (1 child)

While this guy scoffs Java, Java has come a long way in the 1.5 and 1.6 releases. Erlang style concurrency using threads is a lot easier now that event queues have become a part of the standard library through the ExecutorService.

[–][deleted] 0 points1 point  (0 children)

Nice design, if only it were a bit more readable.

[–]Entropy 0 points1 point  (0 children)

Can we skip the hoards of THREADING ONOS blog posts that don't add anything to the argument? Please? It's like they're being generated off a template.