Hi Joe-
Joe St Sauver wrote:
> <stuff deleted>
>
> Either the app needs to be able to analyze and automatically select the
> best server (from among multiple possible servers) based on connectivity,
> or we need to do a far better job of helping users to know what is and
> what isn't I2 connected.
>
> Users won't pick I2 connected servers if they can't tell what is and isn't
> connected via I2.
>
Exactly. So why can't there be a library that characterizes connectivity between a
local host and some set of remote hosts? Possibly a one-sided protocol, but it
might look a lot like the tuning algorithm Web100 employees to tune its TCP
parameters...I'm thinking in broad strokes here, but if a P2P app periodically
characterized it's connections to it's peers (or there was a cool tool/applet that
would do the same and tell you which mirror would serve you best...) it could form
a basis for a self-organizing net that at least encouraged use of the best
connection at a given time. I can quickly think of a number of interesting knobs
such a library could implement to manage its own resources or those connecting to
it.
Sounds like a [grad]student project...(I would not be surprised if someone actually
already pursued this..)
Jerry
>
> Regards,
>
> Joe
|