Git with a cup of tea, painless self-hosted git service Mirror for internal git.with.parts use https://git.with.parts
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.
 
 
 
 
 
 
gitea/vendor/github.com/Microsoft/go-winio
6543 86e2789960
Vendor Update (#16121)
4 years ago
..
pkg/guid [Vendor] Update directly used dependencys (#15593) 4 years ago
.gitignore go1.16 (#14783) 4 years ago
CODEOWNERS [Vendor] Update directly used dependencys (#15593) 4 years ago
LICENSE go1.16 (#14783) 4 years ago
README.md Vendor Update (#16121) 4 years ago
backup.go go1.16 (#14783) 4 years ago
ea.go go1.16 (#14783) 4 years ago
file.go go1.16 (#14783) 4 years ago
fileinfo.go [Vendor] Update directly used dependencys (#15593) 4 years ago
go.mod [Vendor] Update directly used dependencys (#15593) 4 years ago
go.sum [Vendor] Update directly used dependencys (#15593) 4 years ago
hvsock.go [Vendor] Update directly used dependencys (#15593) 4 years ago
pipe.go go1.16 (#14783) 4 years ago
privilege.go [Vendor] Update directly used dependencys (#15593) 4 years ago
reparse.go go1.16 (#14783) 4 years ago
sd.go go1.16 (#14783) 4 years ago
syscall.go [Vendor] Update directly used dependencys (#15593) 4 years ago
zsyscall_windows.go [Vendor] Update directly used dependencys (#15593) 4 years ago

README.md

go-winio Build Status

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.