Doing a scalable, practical P2P file transfer is very non-trivial, even from a purely technical point of view (not touching the ugly politics of it all). The Gnutella people screwed it up for years. Further, most of the scalable P2P apps that are out there have been re-implementing each others' ideas and calling them different things (look particularly at what Freenet calls "CHK"--similar ideas are used in almost every P2P app around, except the simple-stupid ones). So don't add to the mess. As hard as it is, many people have already created good solutions, and you'll do well to find them.

----
send money to your kernel via the boot loader.. This and more wisdom available from Markov Hardburn.

In reply to Re: Multi Stream File Transfer by hardburn
in thread Multi Stream File Transfer by camerlengo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.