What exactly would you want the transferqueue to do in the context of actors? Or are you just looking for potential usage patterns without having a concrete idea yet?

I could imagine it to be used to implement some kind of synchronous bang method on actors, in which the bang method doesn't return immediately, but only after the actor has taken the message out of the queue. On the other hand... is that something usefull in the actor model?

Or is there something else you were thinking of?

Updating tickets (#22, #39, #62, #64, #72, #87, #97, #112, #137, #167, #182, #193, #196, #197, #201, #217, #229, #233, #245, #158)

Used LinkedTransferQueue for the unbounded case,
and wrap LinkedTransferQueue and bound it with a Semaphore for the bounded case

Scrutinize this: http://github.com/jboner/akka/blob/deb8a1fc851e716ab66b53ed8139e969b2cf5467/akka-core/src/main/scala/dispatch/Queues.scala

Pushed a branch where ThreadBasedDispatcher is using TransferQueue, please have a look: http://github.com/jboner/akka/tree/transfer_queue

Rewrote ThreadBasedDispatcher to use actorref.mailbox:

http://github.com/jboner/akka/tree/transfer_queue

Updated ThreadBasedDispatcher in master

close?