Adam Fisk wrote:
I'm actually talking about the monolithic BitTorrent "protocol" lump of
many different pieces of functionality. There are IETF standards for
file downloading, NAT/firewall traversal, and even resource publishing
and lookup each of which better addresses the various pieces of
BitTorrent functionality and each of which interoperates with more than
just other BitTorrents out there. HTTP is the quintessential example.
BitTorrent made the design decision to break interoperability with the
entire rest of the Internet through not using HTTP for file transfers,
making every web server out there an invalid source for a file. The
reason is tit-for-tat and distributing updated source data, but those
don't come anywhere near justifying it in my mind. File transfer, NAT
negotiation, source publishing and lookup, etc, should all properly be
separate protocols as they are in the IETF stack.
Sounds like you are talking about OCN: http://open-content.net/specs/
I don't know if the current version of Swarmcast still implements this
stuff. At this point I think it's too late; BitTorrent beat
HTTP-swarming like Skype beat SIP.
Wes Felter - [EMAIL PROTECTED]
_______________________________________________
p2p-hackers mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/p2p-hackers
