I fully support this change, and would even appreciate a big warning (to be
encoding-aware) on functions that send/receive Strings over the network.
On Wed, Oct 27, 2010 at 6:03 PM, Johan Tibell
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 http://hackage.haskell.org/package/network-bytestring
Discussion deadline: 2 weeks
Johan _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries