open-nomad/vendor/github.com/Microsoft/go-winio
Danielle Lancashire 0ff27cfc0f
vendor: Use dani fork of go-winio
2019-06-28 13:47:18 +02:00
..
pkg/guid vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
LICENSE Update vendor package github.com/fsouza/go-dockerclient 2016-09-24 21:53:49 +02:00
README.md Update vendor package github.com/fsouza/go-dockerclient 2016-09-24 21:53:49 +02:00
backup.go fifo: add new fifo package for named pipes (#4665) 2018-10-16 16:53:30 -07:00
ea.go fifo: add new fifo package for named pipes (#4665) 2018-10-16 16:53:30 -07:00
file.go vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
fileinfo.go fifo: add new fifo package for named pipes (#4665) 2018-10-16 16:53:30 -07:00
go.mod vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
go.sum vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
hvsock.go vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
pipe.go vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
privilege.go Update go-winio to get Microsoft/go-winio#48 2017-05-03 15:22:55 -07:00
reparse.go Update vendor package github.com/fsouza/go-dockerclient 2016-09-24 21:53:49 +02:00
sd.go Update go-winio to get Microsoft/go-winio#48 2017-05-03 15:22:55 -07:00
syscall.go vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00
zsyscall_windows.go vendor: Use dani fork of go-winio 2019-06-28 13:47:18 +02:00

README.md

go-winio

This repository contains utilities for efficiently performing Win32 IO operations in Go. Currently, this is focused on accessing named pipes and other file handles, and for using named pipes as a net transport.

This code relies on IO completion ports to avoid blocking IO on system threads, allowing Go to reuse the thread to schedule another goroutine. This limits support to Windows Vista and newer operating systems. This is similar to the implementation of network sockets in Go's net package.

Please see the LICENSE file for licensing information.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Thanks to natefinch for the inspiration for this library. See https://github.com/natefinch/npipe for another named pipe implementation.