Should I host a direct FTP or HTTP for each patch (not including the client, hell no), how many people would use it? While I know using uTorrent (MicroTorrent) isn't hard in most situations, sometimes you need to get the patches from a unilateral source.
For example: I work at a LAN center, and at such a place, uploads tend to cause tetchy network to get more tetchy until the whole tetchy thing falls over and screams till I promise not to touch it's upload anymore.
Okay, so it isn't that bad.. Aaanyway. If I were to host something like that, how many people would use it? I need to consider how many connections and the bandwidth involved. I've got hosting with DreamHost, who tends to get mad if I open it up too much. I also have my home network as well that I could put on an FTP server and hope it doesn't kill things.
For example: I work at a LAN center, and at such a place, uploads tend to cause tetchy network to get more tetchy until the whole tetchy thing falls over and screams till I promise not to touch it's upload anymore.
Okay, so it isn't that bad.. Aaanyway. If I were to host something like that, how many people would use it? I need to consider how many connections and the bandwidth involved. I've got hosting with DreamHost, who tends to get mad if I open it up too much. I also have my home network as well that I could put on an FTP server and hope it doesn't kill things.
