@@ -38,7 +38,7 @@ The first demo, `demo0` yields the following output:
38 logServer: [Chunk "hello 7" Empty]
38 logServer: [Chunk "hello 7" Empty]
39 logServer: [Chunk "hello 8" Empty]
39 logServer: [Chunk "hello 8" Empty]
40 logServer: [Chunk "hello 9" Empty]
40 logServer: [Chunk "hello 9" Empty]
41− logServer: [Chunk "hello 10" Empty
41+ logServer: [Chunk "hello 10" Empty]
43See the source code for more details.
43See the source code for more details.
@@ -52,7 +52,7 @@ This is demonstrated using the `demo1` function:
53The output of the example is as follows:
53The output of the example is as follows:
55− *DemoProcess> demo1
55+ *DemoProcess> demo1
56 "Starting node"
56 "Starting node"
57 "Starting process"
57 "Starting process"
58 1: jim1 says: hi there
58 1: jim1 says: hi there
@@ -86,10 +86,10 @@ which then outputs some data.
89−The Transport.TCP backend uses Network.ByteString.Lazy as its undelying
89+The `Transport.TCP` backend uses `Network.ByteString.Lazy` as its underlying
90protocol, so we produce a benchmark that compares it directly with this.
90protocol, so we produce a benchmark that compares it directly with this.
91−Furthermore, the Data.Binary package is used for converting values
91+Furthermore, the `Data.Binary` package is used for converting values
92−to ByteStrings for transmission.
92+to `ByteStrings` for transmission.
94The benchmarking is performed on the client side using criterion:
94The benchmarking is performed on the client side using criterion:
95the server must be set up before benching is performed.
95the server must be set up before benching is performed.