[*] Update path notes in readme
This commit is contained in:
parent
c6e6c1c433
commit
ac69c4c2ff
@ -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
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user