in reply to Bandwidth upload sharing

Thanks for the information everyone. I'm going to investigate all of these options. I do have something to add.

If possible, I would like to modify the existing website as little as possible. Changing the links to content on thousands of archived pages would require a lot of work.

Namely, my hope was the run the sharing-server, and then start the normal apache website within it. HTTP requests come to the share-server first, it forwards them into the Apache server within itself, the Apache issues a response, and the share-server has one of the node-sharing-clients fulfill the request.

Are any of the options particularly well suited for this?

Replies are listed 'Best First'.
Re^2: Bandwidth upload sharing
by NetWallah (Canon) on Oct 15, 2007 at 04:03 UTC
    Let me try to paraphrase, and restate your requirements, then analyze them.

    • You have your "normal apache web server" - let us refer to this as the "web server"
    • Then you have the "sharing-server", which, by coincidence/design may reside on the same hardware. Let us call this the "reverse web proxy", since that seems to be it's function. (Web requests hit there first).
    • In addition, you have a bunch of "volunteer" "node-sharing-clients". To me, this should be considered equivalent to a "web farm".

    If we agree on the terminology, this is a fairly standard setup, except for the fact that the web farm comprises of voluntary machines that may appear and disappear. The purpose of the "web server" is to provide the "master" set of files.

    The only additional suggestion I have is that you consider BitTorrent as a mechanism for re-distributing the web server content to the web farm.

         "As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom

[reply]

In Section Seekers of Perl Wisdom