gregandev
/
k3d
mirror of https://github.com/k3d-io/k3d
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
1072 Commits
25 Branches
165 Tags
70 MiB
 
 
 
 
Tag: Branch: Tree: 17dc4b7b4d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '17dc4b7b4d'
${ noResults }
k3d/tools/vendor/github.com/Microsoft/go-winio
History
iwilltry42 0593cfd8c0
integrate k3d-tools repo as Go submodule 		4 years ago
..
.gitignore integrate k3d-tools repo as Go submodule 4 years ago
LICENSE integrate k3d-tools repo as Go submodule 4 years ago
README.md integrate k3d-tools repo as Go submodule 4 years ago
backup.go integrate k3d-tools repo as Go submodule 4 years ago
ea.go integrate k3d-tools repo as Go submodule 4 years ago
file.go integrate k3d-tools repo as Go submodule 4 years ago
fileinfo.go integrate k3d-tools repo as Go submodule 4 years ago
pipe.go integrate k3d-tools repo as Go submodule 4 years ago
privilege.go integrate k3d-tools repo as Go submodule 4 years ago
reparse.go integrate k3d-tools repo as Go submodule 4 years ago
sd.go integrate k3d-tools repo as Go submodule 4 years ago
syscall.go integrate k3d-tools repo as Go submodule 4 years ago
zsyscall_windows.go integrate k3d-tools repo as Go submodule 4 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.