networking possible to use websockify ? #1157
-
|
benjamincburns/websockproxy is recommended in the networking doc |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
No, because v86' networking is based on Layer 2 (ie. sends/receives an Ethernet frames to/from the proxy, and websockproxy replicates all networking base: DHCP server, DNS server etc.) while websockify is based on almost Layer 4 (from README: "At the most basic level, websockify just translates WebSockets traffic to normal socket traffic") |
Beta Was this translation helpful? Give feedback.
-
|
thank you for the clarification |
Beta Was this translation helpful? Give feedback.
-
|
Wisp as a protocol is similar to websockify, just multiplexed (sending multiple TCP streams in one websocket for performance reasons), and can be used now. I actually used websockify initially while writing wisp_network.js, if you remove the wisp code and create a new WebSocket() for each TCP stream it will work. It shouldn't be a big task if you're still interested |
Beta Was this translation helpful? Give feedback.
-
|
Super ancient code now, and messy as can be (this was my first prototype) but this is a modified fetch_network.js which creates a new WebSocket for each TCP stream at wss://server/hostname:port, like websockify but giving the target to the server instead of it being hard coded. It can be modified to use websockify pretty easily |
Beta Was this translation helpful? Give feedback.
No, because v86' networking is based on Layer 2 (ie. sends/receives an Ethernet frames to/from the proxy, and websockproxy replicates all networking base: DHCP server, DNS server etc.) while websockify is based on almost Layer 4 (from README: "At the most basic level, websockify just translates WebSockets traffic to normal socket traffic")