Push changeset data to proxy servers after commit
Single remote workers switching changesets with average download speeds have to wait a long time to grab new changesets for the first time when using proxy server.
Proxy server should have the data pushed to it from the plastic server, since the remote user may not always want the changeset immediately there is plenty of time to upload before the remote user is ready to switch to it.
Really interesting idea.
But it must be the proxy the one actively downloading once being notified somehow by the server, right?? I mean, normally the central server won't reach the proxy because of network topology in my experience.