putAsync/takeAsync should return a Promise

[tmtxt]

Just like their names, these functions should return a Promise (maybe when no callback function specified)

• putAsync
• takeAsync

Use with es7 async/await function

await putAsync(ch, 42);
...
var res = await takeAsync(ch);

Use with other libraries like co

yield putAsync(ch, 42);
...
var res = yield takeAsync(ch);

[XVincentX]

I totally agree with this - I would probably get rid of the callbacks completely, but that would be a breaking change
@hung-phan - any thoughts from your side?

[hung-phan]

Quite a big change, but let me see if I could support it. By the way, I don't use putAsync much, I usually just create a go block and use put.

[XVincentX]

From my personal side, I also do not use it that much (there are some edge cases where I should).

Just out of curiosity, are you using js-csp in production somewhere? Are you willing to share some informations, eventually @hung-phan

[hung-phan]

Ah I just use it for some companies project (not open-source) to handle complex state. For example, implement the behavior of Om cursor (but I think they already go with query expression) to control the application state, implement pubsub like flux, or use it with redux.

[tmtxt]

Many projects are already written in koa/co (in our company projects) and it's would be nice if we can still follow our own coding style instead of wrapping inside one go block (1 more nested level).

Btw, js-csp can be helpful in batch processing and memory constraint environment where we would force one task to wait for another task to finish processing the data before it can continue (or drop the data) using the channel instead of pushing too much data into the queue and fill up the memory.

[ubolonton]

One way to go about this is to provide alternatives to process.js, which integrate with different coroutine systems instead of implementing one (which is basically what process.js does), then make the choice configurable somehow. Most of the integration should be straightforward, except for how errors are handled/propagated.

[XVincentX]

Does anybody of you have nice experience of using CSP to handle complex User Interface scenarios?

[hung-phan]

yes 🤔

[XVincentX]

@hung-phan Cool - are you willing to share some informations? I would be really interested.

[corporatepiyush]

@XVincentX refer this article for using CSP in UI with ReactJS
http://lucasmreis.github.io/blog/using-csp-as-application-architecture/