On Sat, Sep 4, 2010 at 7:14 PM, Ted Ts'o <tytso@mit.edu> wrote:
quoted text
> At least
> where I live, my local ISP (Comcast, which is very common internet
> provider in the States) deliberately degrades the transfer of
> peer2peer downloads.

 if microsoft can add ncacn_http to MSRPC for the exact same sorts of
reasons, and even skype likewise provides a user-config option to
specify "port 80" or port "3128", then it's perfectly possible to do
likewise. ncacn_http actually has HTTP 1.1 headers on it, and, once
you've negotiated enough to look like HTTP, the raw socket is hander
over to MSRPC for it to play with.

quoted text
> Which brings me back to my original question --- what problem exactly
> are you trying to solve?  What's the scenario?

i described those in prior messages.  to summarise: they're basically
reduction of dependence on centralised infrastructure, and to allow
developers to carry on doing code-sprints using bugtrackers, wikis and
anything else that can be "git-able" as its back-end, _even_ in the
cases where there is little or absolutely no bandwidth... and _still_
sync up globally once any one of the developers gets back online.

 so i'm _not_ just thinking of the "code, code, code" scenario, and
i'm not just thinking in terms of the single developer "i code,
therefore i am" scenario.  i'm thinking of scenarios which increase
the productivity of collaborative development even in the face of
unreliable or non-existent connectivity [carrier pigeons...]

l.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html