Re: Musings on RxAda

[brbarkstrom@gmail.com]

This approach may also tie in with the communities working on "Asynchronicity".
They would like to create interfaces that identify "Promises" that appear to
be unelaborated tasks.  When a user responds to a message, the controlling
task elaborates the fulfilled promise (of a response to an asynchronous
message and lets the elaborated task work.

See, for example,
<crockford.com/pp/asynchronicity.pptx>
or
<http://webapplog.com/asynchronicity-in-node-js/>
A site that discusses "Promises" in javascript is
<http://12devs.co.uk/articles/promises-an-alternative-way-to-approach-asynchronous-javascript/>
It looks like the use of "Promises" is to provide a low cost way of
formalizing responses to asynchronous I/O.

Bruce B.