On Fri, Jan 17, 2020 at 09:38:42AM +, Daniel P. Berrangé wrote:
> On Fri, Jan 17, 2020 at 10:27:05AM +0100, Pavel Hrdina wrote:
> > On Thu, Jan 16, 2020 at 03:24:41PM +, Daniel P. Berrangé wrote:
> > > Windows sockets take a SOCKET HANDLE object instead of a
> > > file descriptor. Wrap
On Fri, Jan 17, 2020 at 10:27:05AM +0100, Pavel Hrdina wrote:
> On Thu, Jan 16, 2020 at 03:24:41PM +, Daniel P. Berrangé wrote:
> > Windows sockets take a SOCKET HANDLE object instead of a
> > file descriptor. Wrap them in the same way that gnulib
> > does so that they use C runtime file
On Thu, Jan 16, 2020 at 03:24:41PM +, Daniel P. Berrangé wrote:
> Windows sockets take a SOCKET HANDLE object instead of a
> file descriptor. Wrap them in the same way that gnulib
> does so that they use C runtime file descriptors.
>
> While we could in theory use GSocket, it is hard to get
>
Windows sockets take a SOCKET HANDLE object instead of a
file descriptor. Wrap them in the same way that gnulib
does so that they use C runtime file descriptors.
While we could in theory use GSocket, it is hard to get
the exact same semantics libvirt has for its current
socket usage. Wrapping the
