|
Boost : |
From: Don G (dongryphon_at_[hidden])
Date: 2005-04-13 22:14:39
I think this presupposes a mostly manual association of
selectable_object with select_set? The select_set is then used to
wait? If not, please explain the importance of "when can non-blocking
operations proceed" vs. "async operations are done". If the
"operation is done" callback occurs by calling dequeuing a
boost::function<> then the app is still "single threaded" to the
user.
Seeking understanding,
Don
--- Iain Hanson <Iain.Hanson_at_[hidden]> wrote:
> On Wed, 2005-04-13 at 11:09 -0400, Caleb Epstein wrote:
> > On 4/13/05, Don G <dongryphon_at_[hidden]> wrote:
> > > I also believe that non-blocking is an I/O only thing; it is
> not
> > > needed for connect or accept.
> >
> > Not sure about the need for a non-blocking accept, but a
> non-blocking
> > connect is a must-have.
> >
> Non blocking accept is also a must have for single threaded
> reactive
> servers.
>
> /ikh
> > _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk