* Paul LeoNerd Evans [2013-05-27 01:35]:
> On Sat, 25 May 2013 08:52:30 +0200
> Aristotle Pagaltzis wrote:
>
> > That’s just what futures are for, I think? As in, they abstract the
> > sync/async control flow out of the code. And you’re just putting that
> > on top of one common HTTP client API p
On Sat, 25 May 2013 08:52:30 +0200
Aristotle Pagaltzis wrote:
> That’s just what futures are for, I think? As in, they abstract the
> sync/async control flow out of the code. And you’re just putting that
> on top of one common HTTP client API pattern. It seems like discovery
> rather than inventi
* Paul LeoNerd Evans [2013-05-23 23:15]:
> The whole module would work easily as well given any other type of
> object with this API, including anything that is actually synchronous,
> such as a tiny wrapper around LWP:
>
> package LWP::FutureReturning;
> use base qw( LWP::UserAgent );
> use Fu
