Proposal: Merge network-bytestring into network

wren ng thornton wren at
Wed Oct 27 19:37:00 EDT 2010

On 10/27/10 6:03 PM, Johan Tibell wrote:
> Hi all,
> network-bytestring addresses two serious problems with the network
> package: performance and a semantically incorrect type for network
> data. Both problems are addressed by using ByteStrings instead of
> Strings in the types of e.g. recv and send. In addition,
> network-bytestring supports vectored I/O (also know as scatter/gather
> I/O) which yields better performance in many common use cases, such as
> HTTP servers.
> The merge doesn't break any old code: it introduces new APIs under
> Network.Socket.ByteString and Network.Socket.ByteString.Lazy but
> leaves the old API intact. The network-bytestring package is also
> better documented and tested that the network package. The API is
> portable.
> The network-bytestring package can be found at
> Discussion deadline: 2 weeks


My only request would be to update the documentation for the old network 
functions in order to (a) make them match the quality of the docs in 
network-bytestring, and (b) to warn people that they should be using the 
bytestring functions anyways.

Live well,

More information about the Libraries mailing list