Why would you claim composable futures are indeed a component of FRP? I find no mention of this in Elliott's and/or Hudak's description of FRP.

Edit:

Conal adds a notion of future values in his push/pull work, but I wonder if it is the same thing as being discussed here, as composable futures were around long before FRP:

http://conal.net/papers/push-pull-frp/push-pull-frp.pdf

I was thinking more of their iteratee stuff:

https://github.com/playframework/playframework/tree/master/f...

Again, don't know the state of pulling it apart but earlier versions were tied to Play in name only.

The first example of reactive programming in Wikipedia is the ability to define a = b + c, where b and c are changing (and a is changing with them. In Quasar, you can do it imperatively:

  for(;;)
      a.send(b.receive() + c.receive();

Or functionally:

   zip(b, c, (x, y) -> x + y);

RxJava also lets you do the latter. I see that it could also be achieved with a combination of Iteratees and Enumeratees in the code you linked to, using an approach similar to RxJava's, only more complicated and with fewer features.

Play's futures are just Scala futures, they aren't tied to HTTP requests.