Don't send the data over socket connection

A better way could be to setup an orchestration process via JobScheduler or some-other interface. Then use a queue-pull type mechanism, or HDFS, maybe. An even MORE interesting method could be a cache-like FS for the browser to save chunks client-wise from the server initially, and stream the data and fork data continuously through a job queue/pipe like mechanism.

Also, how about chain clients in a circular-hash... so when a client joins/drops-out, things can be easily maintained (in job/data space).