undefined | Better HN

0 pointsjrochkind14y ago0 comments

Hmmm... would it be possible to write an ftp client in browser JS? I think probably not.

0 comments

Yes, you can build an FTP client in JavaScript. However the browser won't let you escape the sandbox and open an arbitrary port ... but on Node.js or FirefoxOS (haha) there shouldn't be a problem, except weirdness in standard interpretation :)

liketochill4y ago

I don’t program web sites or web browsers, but with wasm or web sockets can’t you make a web page that opens a connection and sends arbitrary binary data to another server without any http?

duskwuff4y ago

No. WebSockets are a specific protocol tunneled over HTTP, not raw sockets, and WASM doesn't expose any functionality which wasn't already available to JS.

liketochill4y ago

Webrtc?

1 more reply

handrous4y ago

Last I checked you'd still be speaking HTTP (even if it's "WebSockets"), not raw TCP. Certainly there's no UDP support. You'd need a translating proxy of some kind.

notamy4y ago

> but with wasm or web sockets can’t you make a web page that opens a connection and sends arbitrary binary data to another server without any http?

I can't speak to WASM, but websockets are literally just a layer over HTTP in some regards -- a websocket connection is initiated by sending an HTTP request with the Upgrade header.

ForHackernews4y ago

You watch, eventually everything be a layer over HTTPS[0], and 443 will be the only port. RIP Internet.

[0] https://en.wikipedia.org/wiki/DNS_over_HTTPS

j / k navigate · click thread line to collapse

0 comments

johannes12343214y ago

liketochill4y ago

I don’t program web sites or web browsers, but with wasm or web sockets can’t you make a web page that opens a connection and sends arbitrary binary data to another server without any http?

duskwuff4y ago

No. WebSockets are a specific protocol tunneled over HTTP, not raw sockets, and WASM doesn't expose any functionality which wasn't already available to JS.

liketochill4y ago

Webrtc?

1 more reply

handrous4y ago

Last I checked you'd still be speaking HTTP (even if it's "WebSockets"), not raw TCP. Certainly there's no UDP support. You'd need a translating proxy of some kind.

notamy4y ago

> but with wasm or web sockets can’t you make a web page that opens a connection and sends arbitrary binary data to another server without any http?

I can't speak to WASM, but websockets are literally just a layer over HTTP in some regards -- a websocket connection is initiated by sending an HTTP request with the Upgrade header.

ForHackernews4y ago

You watch, eventually everything be a layer over HTTPS[0], and 443 will be the only port. RIP Internet.

[0] https://en.wikipedia.org/wiki/DNS_over_HTTPS

j / k navigate · click thread line to collapse