Little helper to run CNCF's k3s in Docker
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
k3d/vendor/github.com/Microsoft/go-winio
iwilltry42 f39a9513fd
dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package
4 years ago
..
pkg/guid try interface 5 years ago
vhd dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package 4 years ago
.gitignore try interface 5 years ago
LICENSE try interface 5 years ago
README.md try interface 5 years ago
backup.go try interface 5 years ago
ea.go try interface 5 years ago
file.go try interface 5 years ago
fileinfo.go try interface 5 years ago
go.mod dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package 4 years ago
go.sum dependencies: update docker dependencies to fix issues with failing windows builds introduced by the usage of the archive package 4 years ago
hvsock.go try interface 5 years ago
pipe.go try interface 5 years ago
privilege.go try interface 5 years ago
reparse.go try interface 5 years ago
sd.go try interface 5 years ago
syscall.go try interface 5 years ago
zsyscall_windows.go try interface 5 years ago

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.