Implemented support for logging to TCP endpoints.

README.md

@@ -11,7 +11,8 @@
 
 <!-- cargo-rdme start -->
 
-`dirty-debug` offers a quick and easy way to log message to a file for debugging.
+`dirty-debug` offers a quick and easy way to log message to a file (or tcp endpoint) for
+temporary debugging.
 
 A simple but powerful way to debug a program is to printing some messages to understand your
 code’s behavior.  However, sometimes you don’t have access to the `stdout`/`stderr` streams (for
@@ -28,4 +29,19 @@ message to that file, together with the filename and line number of the source c
 Note that this is not meant to be a normal form of logging: `dirty-debug` should only be used
 temporarily during your debug session and discarded after that.
 
+## Logging to a TCP endpoint
+
+You can also use `dirty-debug` to log to a TCP endpoint instead of a file:
+
+```rust
+ddbg!("tcp://192.168.1.42:12345", "Hello!");
+```
+
+Probably the easiest way to listen to a TCP endpoint in the target computer is by using netcat:
+
+```console
+$ ncat -l 12345
+[src/lib.rs:123] Hello!
+```
+
 <!-- cargo-rdme end -->