Description
Highly concurrent drop-in replacement for bufio.Writer.
Writer implements highly concurrent buffering for an io.Writer object. In particular, writes will not block while a Flush() call is in progress as long as enough buffer space is available.
concurrent-writer alternatives and similar packages
Based on the "Files" category.
Alternatively, view concurrent-writer alternatives based on common mentions on social networks and blogs.
-
go-storage
A vendor-neutral storage library for Golang: Write once, run on every storage service. -
bigfile
Bigfile -- a file transfer system that supports http, rpc and ftp protocol https://bigfile.site -
-
-
go-exiftool
Golang wrapper for Exiftool : extract as much metadata as possible (EXIF, ...) from files (pictures, pdf, office documents, ...) -
-
skywalker
A package to allow one to concurrently go through a filesystem with ease -
-
tarfs
An implementation of the FileSystem interface for tar files. -
fileconversion
A Go library to convert various file formats to plaintext and provide related functions -
-
shred
This is a libary to mimic the functionallity of the linux shred command. -
go-staticfiles
Collects assets (css, js, images...) from a different locations and tags file names with a hash for easy versioning and aggressive caching. -
Static code analysis for 29 languages.
Do you think we are missing an alternative of concurrent-writer or a related project?
|
Build time-series-based applications quickly and at scale.
sponsored
www.influxdata.com
|
Popular Comparisons
-
concurrent-writervsgo-csv-tag
-
concurrent-writervsDXF-go
-
concurrent-writervsgo_MD5
-
concurrent-writervstarfs
-
concurrent-writervsgo-gtfs
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
concurrent-writer 
Highly concurrent drop-in replacement for bufio.Writer.
concurrent.Writer implements highly concurrent buffering for an io.Writer object.
In particular, writes will not block while a Flush() call is in progress as
long as enough buffer space is available.
Note however that writes will still block in a number of cases, e.g. when another write larger than the buffer size is in progress. Also, concurrent flushes (whether explicit or triggered by the buffer filling up) will block one another.