Re: [boost] [defer] - comments?

From: Oliver.Kowalke_at_[hidden]
Date: 2007-03-14 07:46:49

This points to the ongoing futures debate. If the interface and features
are clear then it could be incorporated into the defer library.
Oliver

> -----Original Message-----
> From: boost-bounces_at_[hidden] 
> [mailto:boost-bounces_at_[hidden]] On Behalf Of Rodrigo 
> Pinho Pereira de Souza
> Sent: Wednesday, March 14, 2007 12:32 PM
> To: boost_at_[hidden]
> Subject: Re: [boost] [defer] - comments?
> 
> I will start use in my project today. I have tested your test 
> project yestarday, and it works fine.
> I am only missing an way to get result of function, so I will 
> just create functions which put results in a queue, and main 
> thread will get that results.
> 
> 
> 
> On 1/27/06, simon meiklejohn <simon_at_[hidden]> wrote:
> >
> > Anyone had a play with the defer library in the vault and want to 
> > comment on its usefulness?
> >
> > It clearly shares much in common with the asio Dispatcher 
> concept but 
> > with the freedom to define more general Dispatchers. (e.g. 'Create 
> > thread per callback' and 'Dispatch Callback via Message 
> Pump', both of 
> > which violate the specific guarantees of the asio 
> Dispatcher concept, 
> > that the callback occur in a thread that has called 
> > asio::demuxer::run().)
> >
> > One potential application for defer would be in conjunction 
> with asio, 
> > creating the thread(s) which call demuxer::run() in a succinct form.
> >
> > Cheers
> >
> > Simon
> >
> >
> >
> >
> > _______________________________________________
> > Unsubscribe & other changes:
> > http://lists.boost.org/mailman/listinfo.cgi/boost
> >
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost
>