Recent submissions

Comment · 3 months ago
Congrats on shipping :)
Comment · 10 years ago
Comment · 10 years ago
They will. However, if you take a look at the final code snippet, you'll see we're not relying on any minified name. The public interface of modules remains intact through minification.
Comment · 12 years ago
Because it's much easier to implement?
Comment · 13 years ago
I just did, thanks :)
Comment · 13 years ago
There is no built-in failover mechanism atm. However I guess you could use another program on top of dispatch to implement such a feature.
Comment · 13 years ago
Yup.
Comment · 13 years ago
Adding it now.
Comment · 13 years ago
One of the advantages of using a proxy is that you can configure it per app.

For example, let's say I have 3 interfaces.

Interfaces (1) and (2) are low-latency and interface (3) is high latency.

I can start a proxy on localhost:1080 that redirects to interfaces (1), (2) and (3), and configure my download manager to use it.

I can then start another proxy on localhost:1081 that redirects to interfaces (1) and (2), and configure my game client to use it.

Comment · 13 years ago
Windows, Mac OS X and Linux.

Every platform which runs NodeJS in fact.

Comment · 13 years ago
For now, the proxy will still try to dispatch sockets to every network interfaces specified at launch. But such a feature could perfectly be implemented.
Comment · 13 years ago
At the TCP level.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton