|
Boost : |
From: williamkempf_at_[hidden]
Date: 2001-06-27 12:40:27
--- In boost_at_y..., "Peter Dimov" <pdimov_at_m...> wrote:
> From: "John Max Skaller" <skaller_at_o...>
>
> > Greg Colvin wrote:
> >
> > > Because killing threads is a bad idea.
> >
> > No, it isn't a 'bad idea'. It is essential
> > in many applications, in particular, it is essential
> > in most multithreaded servers to kill client connection
> > management threads when they're unable to detect that
> > the connection is lost or exceeded some bound
> > (such as 'out of money').
> >
> > A thread blocked waiting for input
> > cannot always detect such conditions (only an actual
> > input error). In such cases, cancellation is not
> > a bad idea, it is mandatory.
>
> But does thread cancellation unwind the thread stack? If it does,
how is
> this possible to implement without core language support?
Only one of the issues to address, though probably the most important
one (and with use of destructors this one solves some of the others
as well).
Bill Kempf
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk