On Thu, Jun 01, 2017 at 02:23:30PM +0200, Martin Kletzander wrote:
> On Thu, Jun 01, 2017 at 01:10:45PM +0100, Daniel P. Berrange wrote:
> > On Thu, Jun 01, 2017 at 02:02:14PM +0200, Michal Privoznik wrote:
> > > We have couple of wrappers over our low level stream APIs:
> > > virSreamRecvAll(), vi
On Thu, Jun 01, 2017 at 01:10:45PM +0100, Daniel P. Berrange wrote:
On Thu, Jun 01, 2017 at 02:02:14PM +0200, Michal Privoznik wrote:
We have couple of wrappers over our low level stream APIs:
virSreamRecvAll(), virStreamSendAll() and their sparse stream
variants. All of them take some callbacks
On Thu, Jun 01, 2017 at 02:02:14PM +0200, Michal Privoznik wrote:
> We have couple of wrappers over our low level stream APIs:
> virSreamRecvAll(), virStreamSendAll() and their sparse stream
> variants. All of them take some callbacks and call them at
> appropriate times. If a callback fails it abo
We have couple of wrappers over our low level stream APIs:
virSreamRecvAll(), virStreamSendAll() and their sparse stream
variants. All of them take some callbacks and call them at
appropriate times. If a callback fails it aborts the whole
operation. However, if it so happens that the callback fails