[457] in Pthreads mailing list archive
Re: pthread_cancel points
daemon@ATHENA.MIT.EDU (Christopher Provenzano)
Mon Oct 7 17:51:33 1996
Reply-To: proven@cygnus.com
To: "Larry V. Streepy, Jr." <streepy@healthcare.com>
Cc: pthreads mailing list <pthreads@MIT.EDU>
In-Reply-To: Your message of "Wed, 02 Oct 1996 19:45:04 MDT."
<32531AA0.76AED477@healthcare.com>
Date: Mon, 07 Oct 1996 03:19:29 -0400
From: Christopher Provenzano <proven@proven.org>
> It seems really odd to me that the draft 10 standard list of cancel
> points doesn't include a single network/socket operation.
>
> That seems very wrong. Why would you make "read" a cancel point, but
> not "recv" or "recvmsg". Things like "accept" and "connect" are also
> excluded.
>
> Admittedly, I don't have the whole spec, just certain sections.
>
> So, am I missing something, or does the spec specifically ignore socket
> operations?
The POSIX thread standard POSIX 1003.1c is an extension of the
POSIX 1003.1 standard, which didn't include any socket or network
operations. I expect that when the network API is standardized then
those operations will be cancelable but first the have to standardize
what they are.
CAP
