Scala I/O processor

[Daniel Sobral]

There's something I don't quite get about processors... I have an
output I need to do asynchronously. It's just a fire&forget thing, but
it's called from on asynchronous handlers from netty, so I can't
block.

Now, the question I have is... does execute() block? If so, how can I
accomplish the above?

--
Daniel C. Sobral

I travel to the future all the time.

[Jesse Eichar]

If you want asynchronous behaviour with a processor you need to call future or futureExec.  

Now for the execute() method.  It will recursively force execute all processors.  Suppose your process is a Processor[LongTraversable[Processor[Int]]].  For all the IO to happen all Processors need to be executed.  Execute takes care of that.  This is a possibly a special case but one I encountered while writing tests.   

Naturally the futureExec() does the same thing but asynchronously.  

Jesse

[Daniel Sobral]

I see, thanks. As a feedback, that is not clear from the Scala I/O
docs on asynchronous I/O. Also, the emphasis there is on the read most
of the time, which made it harder to figure out write.

[Jesse Eichar]

Fair points.   I will play around with the idea of how to show the writing process a bit more prominently.

Jesse