On Wed, 2015-06-24 at 16:41 +0100, Ian Jackson wrote:
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
We've discussed the semantics of cancellation a bit more off-list and
have come to two conclusions:
1. [...]
We should rename the proposed
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
We've discussed the semantics of cancellation a bit more off-list and
have come to two conclusions:
1. [...]
We should rename the proposed libxl_ao_cancel() to libxl_ao_abort().
Unless someone objects to this,
Hi,
On Wed, Jan 28, 2015 at 04:57:19PM +, Ian Jackson wrote:
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
On Tue, Jan 20, 2015 at 04:38:24PM +, Ian Jackson wrote:
* Is an API along these lines going to meet your needs ?
The API you propose for
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
Sorry, I didn't think you were waiting for a reply. Your explanation
does answer my questions, thanks.
Oh, good, thanks.
I think that the current proposed behaviour will suit us fine. We will
probably treat the OK and
Ian Jackson writes (Re: Cancelling asynchronous operations in libxl):
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
The API you propose for libxl_ao_cancel, as described in the comment in
libxl.h, looks reasonable to us.The comment for ERROR_NOTIMPLEMENTED
is a
Euan Harris writes (Re: Cancelling asynchronous operations in libxl):
On Tue, Jan 20, 2015 at 04:38:24PM +, Ian Jackson wrote:
* Is an API along these lines going to meet your needs ?
The API you propose for libxl_ao_cancel, as described in the comment in
libxl.h, looks reasonable to
Hi,
On Tue, Jan 20, 2015 at 04:38:24PM +, Ian Jackson wrote:
* Is an API along these lines going to meet your needs ?
The API you propose for libxl_ao_cancel, as described in the comment in
libxl.h, looks reasonable to us.The comment for ERROR_NOTIMPLEMENTED
is a bit confusing: under
