From ac69c4c2fffc958d79774038a6d3357e939443b0 Mon Sep 17 00:00:00 2001 From: Jamie Reece Wilson Date: Sat, 6 Jul 2024 14:13:00 +0100 Subject: [PATCH] [*] Update path notes in readme --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 67af645f..2adce560 100644 --- a/README.md +++ b/README.md @@ -290,16 +290,17 @@ All string paths are simply expanded, similar to MSCRT's `fullpath` or UNIX's `r | `..` | Go up a directory | | `/` | Agnostic Directory Splitter | | `\` | Agnostic Directory Splitter | +| `\\` | Escaped POSIX FS `\` character. | | `.` [SPLITTER] | Nothing | -## * Note, this means sym-links are not traversed until after the path is first made canonical by a naive expansion (read: fast/avoiding sys io+errors) and normalization algorithm.* +## * Note, this implies sym-links are not traversed, until after the path is first made canonical by a naive expansion (read: fast, avoiding system io and system errors) and normalization algorithm.* ### TLS TLS client and partial server support is provided by protocol stack interceptors meaning that our implementation is no-socket. It's possible to write into a buffered protocol stack using the provided stream writer, simulating data coming through a socket channel; -and to fetch the response/translated message using an end protocol piece to be supplied with the data, or using the provided stream reader to read the end -to read the end interceptors buffer once the protocol stack has been ticked. +and to fetch the response/translated message using an end protocol piece to be supplied with the data, or using the provided stream reader +to read the end interceptors buffer, once the protocol stack has been ticked. ### Resources