The network-bytestring package

[Tags:bsd3, deprecated, library]
Deprecated. in favor of network

Fast, memory-efficient, low-level socket functions that use Data.ByteStrings instead of Strings.

[Skip to Readme]


Versions 0.1, 0.1.1,,,,, 0.1.2,, 0.1.3,,,,
Dependencies base (<4.1), bytestring (<1.0), network (>= && <2.3) [details]
License BSD3
Author Johan Tibell <>
Maintainer Johan Tibell <>
Category Network
Home page
Uploaded Sun May 10 17:09:05 UTC 2009 by JohanTibell
Distributions NixOS:
Downloads 4361 total (86 in the last 30 days)
0 []
Status Docs uploaded by user
Build status unknown [no reports yet]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for network-bytestring

Readme for network-bytestring-

Fast and memory efficient low-level networking

The network-bytestring library provides faster and more memory efficient low-level socket functions, using ByteStrings, than those in the network library.



Make sure you read the Haskell Style Guide.

The existing code doesn't follow the style guide fully but you should follow it for all new code.

Creating patches

The preferred way of contributing changes to the project is to use Git and send the patches over email using the Git commands format-patch and send-email. Step by step instructions:

Clone the repository:

git clone

Make your changes:

cd network-bytestring
$EDITOR <file>

Commit your changes in one or more commits:

git add <file>
git commit

Make sure you write a good commit message. Commit messages should contain a short summary on a separate line and, if needed, a more thorough explanation of the change. Write full sentences and use proper spelling, punctuation, and grammar.

You might want to use git rebase to make sure your commits correspond to nice, logical commits. Make sure whitespace only changes are kept in separate commits to ease reviewing.

Prepare the e.g. last five patches for sending:

git format-patch -5 -n

This will create one patch file per patch.

git send-email --to <maintainer> <patch files>

The maintainer is specified in the Cabal file. The maintainer will review your changes and may ask you to make changes to them. Make the changes to your local repository and use git rebase to massage them into nice, logical commits and resend the patches.