diff options
| author | cbdev <cb@cbcdn.com> | 2019-06-08 12:08:55 +0200 |
|---|---|---|
| committer | cbdev <cb@cbcdn.com> | 2019-06-08 12:08:55 +0200 |
| commit | fa51a8db630414292e106369a10bb43c486fddc7 (patch) | |
| tree | 2c9f9d9ee3b2910d3864216d478fff3b191e661c | |
| parent | 3ba33c4b256577be7962dd41b0c8221a0447aef0 (diff) | |
| download | websocksy-fa51a8db630414292e106369a10bb43c486fddc7.tar.gz websocksy-fa51a8db630414292e106369a10bb43c486fddc7.tar.bz2 websocksy-fa51a8db630414292e106369a10bb43c486fddc7.zip | |
Update Readme
| -rw-r--r-- | README.md | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -1,8 +1,10 @@ # websocksy -`websocksy` is a highly configurable [WebSocket (RFC6455)](https://tools.ietf.org/html/rfc6455) to 'normal' networking transport (TCP/UDP) bridge. +`websocksy` is a highly configurable [WebSocket (RFC6455)](https://tools.ietf.org/html/rfc6455) to 'normal' networking transport (TCP/UDP/Unix sockets) bridge. It is written in C and supports pluggable modules for bridge peer selection modules (for dynamic bridging) and stream framing. +It can be used to connect a wide variety of existing applications directly to a website, or to implement new functionality in a way that maintains compatibility between traditional network transports and WebSockets. + Connecting WebSockets to 'real' sockets may seem like an easy task at first, but the WebSocket protocol has some fundamental differences to TCP and UDP. ### Framing |