[concurrency-interest] ForkJoinPool for async http calls?

√iktor Ҡlang viktor.klang at gmail.com
Thu May 10 13:13:48 EDT 2012


On Thu, May 10, 2012 at 7:07 PM, Zhong Yu <zhong.j.yu at gmail.com> wrote:

> On Thu, May 10, 2012 at 10:26 AM, Christian Essl
> <christianessl at googlemail.com> wrote:
> > Your are right my primary concern is code-simplicity not pure
> > performance, basicly writing in a traditional imperative blocking
> > style but still having IO with (mostly) non-blocking threads (and no
> > callbacks, no monadic futures).
>
> Thread is such a nice programming abstraction, it's a shame that we
> are so concerned of its overhead nowadays. Replacing simple threads
> with complex tasks seems to be retrogressing - aren't programming
> supposed to become easier?
>
> What are the fundamental reasons that Java Threads are expensive?
>

Can you give some arguments as to the greatness of proactive programming
(threads)?


>
> Zhong Yu
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>



-- 
Viktor Klang

Akka Tech Lead
Typesafe <http://www.typesafe.com/> - The software stack for applications
that scale

Twitter: @viktorklang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20120510/79fbedf1/attachment.html>


More information about the Concurrency-interest mailing list