RE: Scalaz actors at BFPG (video)

In Tom's example, he only has 2 actor instances: the scalazReceiveActor and scalazSendActor. But then he says he is running on a thread pool with 50 threads. I think this gives the wrong impression that the actors must be handling messages non-sequentially. i.e. that:

scalazReceiveActor ! socket.accept

Can somehow handle multiple connections simultaneously. Of course, this is not the case: the program as designed has an unnecessary bottleneck and can only parse one socket's request at a time.
Chris

> Date: Fri, 10 Dec 2010 08:20:09 +1000
> From: tonymorris@gmail.com
> To: scala-user@listes.epfl.ch
> Subject: [scala-user] Scalaz actors at BFPG (video)
>
> Hello, I help run the Brisbane Functional Programming Group with two
> other guys, Tom Adams and OJ Reeves.
>
> Tom works for a small company doing mobile device development. I don't
> really know much more about what he does specifically, however, he
> recently gave a short (30mins) talk on Scalaz actors because he used for
> something-or-rather in his mobile device development work.
>
> Here is the video:
> http://vimeo.com/17626682
>
> BFPG:
> http://www.meetup.com/Brisbane-Functional-Programming-Group/
>
> --
> Tony Morris
> http://tmorris.net/
>
>