> regards,
> alexander.
>
> -Dimitri Staessens <dimitri.staess...@ugent.be> wrote: -
> To: Alexander Terekhov <terek...@de.ibm.com>
> From: Dimitri Staessens <dimitri.staess...@ugent.be>
> Date: 06/14/2017 01:20PM
> Cc: austin-group-l@opengroup.org
&
sens <dimitri.staess...@ugent.be>
> To: austin-group-l@opengroup.org
> Date:14.06.2017 11:32
> Subject:Fwd: Re: request for clarification on Open Group Base
> Specifications Issue 7: Canc...
>
Hi Geoff,
Awesome service, thanks!
Dimitri
On 06/13/17 13:35, Geoff Clare wrote:
> Dimitri Staessens wrote, on 12 Jun 2017:
>> Is there a way for me to track down the people that are responsible for
>> this adjustment in the specification so that they can comment on
Dimitri Staessens wrote, on 12 Jun 2017:
>
> Is there a way for me to track down the people that are responsible for
> this adjustment in the specification so that they can comment on their
> intentions and motivations for making it?
hat is wrong here.
>
> regards,
> alexander.
>
>
>
> From:Dimitri Staessens <dimitri.staess...@ugent.be>
> To:shwares...@aol.com, austin-group-l@opengroup.org
> Date:11.06.2017 09:08
> Subject: Re: request f
staess...@ugent.be>
To: shwares...@aol.com, austin-group-l@opengroup.org
Date: 11.06.2017 09:08
Subject: Re: request for clarification on Open Group Base
Specifications Issue 7: Canc...
Hi,
Thank you for your response.
On 06/11/17 00:18, shwares...@aol.com wrote:
I don't see the interfac
I don't see the interface invoked to block the thread is allowed to cancel
the request completely, simply that the interface may return to reduce
serialization latencies for the 2 bullet point cases and the cancellation
honored at the next plausible point in the code path, in accordance with