Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Printed | Page 8 Example 1-4 code |
The entire central part of the example code is commented out (C++ style) so will obviously have no functionality when compiled. |
Anonymous | Mar 14, 2014 |
Printed | Page 8 bottom 15 lines |
The bottom 15 lines of code are commented out, but shouldn't be. |
P Jurgensen | Apr 27, 2017 |
Page 55 Figure 2-10 |
In third box in second row it should look like: |
Anonymous | May 01, 2013 | |
Page 82 Figure 3-1 |
Frame 2 should contain "Hello" instead of "Address". |
Anonymous | May 04, 2013 | |
Printed | Page 175 3rd paragraph |
Additionally, we will keep a queue of workers per service should be a queue of client requests |
Richard Williams | May 04, 2014 |
ePub | Page 9999 Code block after Para 1 |
(Note: I put page 9999 because it is a required field - makes no sense on ePub) |
pob | Feb 07, 2015 |
ePub | Page 9999 ch 2, sockets and patterns, messaging patterns, working with messages: |
Near the end of the page, under the last TIP on this page, it says: |
pob | Feb 14, 2015 |