AsyncProcessor?

[squeedee]

AsyncProcessor?

[darscan]

Nice idea. Not possible at the moment, but certainly do-able. Will have a think about how to implement that cleanly. Thanks!

[squeedee]

Is there a technical name for this kind of IoC? Not so much the fluent interface as the inversion by composing closures?

I'm considering perhaps doing the same but composing instances of objects conforming to interfaces.

[squeedee]

Didnt mean to close this :P

[darscan]

Hi Squeedee,

I finally got around to trying out some Async Processing. I decided to use the Node.js-style callback idiom to keep things lightweight. The Promise file itself needs to be cleaned up at some point (naming consistency etc), but here's what I've got for now (in the "callback" branch):

https://github.com/darscan/robotlegs-extensions-Oil/blob/callback/README.textile (see Processing Promises)

https://github.com/darscan/robotlegs-extensions-Oil/blob/callback/src/org/robotlegs/oil/async/Promise.as#L143

The nice thing about this approach is that one can transform a "result" into an "error" via a processor. Let me know what you think.

[hyakugei]

That looks quite interesting - not sure i have a place for it in my current project, but will keep it in mind anytime i have to process any incoming info.

[darscan]

I have merged the callback branch (async result processing) into master.