Changes between Version 9 and Version 10 of Transferring Large Data


Ignore:
Timestamp:
08/28/06 18:05:44 (20 years ago)
Author:
dkg@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Transferring Large Data

    v9 v10  
    3535 * '''old protocols:''' SMTP was really not designed for more than text messages.  The mime extensions are widely implemented, but they are subtly broken in lots of different e-mail software, MTAs and MUAs alike.  Newer protocols (such as http) or old protocols designed to handle arbitrary data (such as FTP) are actually going to be more likely to get your data transferred all in one piece.
    3636 * '''too many cooks in the kitchen:''' often, several different MTAs will handle a single piece of mail before it gets to its destination.  The subtle breakages mentioned above are compounded by the fact that SMTP tends to rely on multiple hops to get the data from sender to receiver.  It's possible for your MUA and MTA to initially do everything right, and then find that some MTA closer to your receipient has garbled your data somehow.
    37  * '''receipient-pays:''' with SMTP, even if you don't want that huge message from someone, it chews up space in your inbox.  Depending on your choice of MUA and your connectivity to the internet, it may even cost you download time or transfer allowance as you fetch the message to decide to delete it.  With larger messages, your inbox quota can be exhausted with fewer mesages, even if you didn't want those messages in the first place.
     37 * '''receipient-pays:''' with SMTP, even if you don't want that huge message from someone, it chews up space in your inbox.  Depending on your choice of MUA and your connectivity to the internet, it may even cost you download time or transfer allowance as you fetch the message to decide to delete it.  With larger messages, your inbox quota can be exhausted with fewer messages, even if you didn't want those messages in the first place.
    3838 * '''sender-pays:''' sending an e-mail with a large attachment to someone who doesn't want it is a waste of time, space, and transfer allowance for the sender (and all intermediate MTAs), since it will be eventually deleted on the other side anyway.  Posting a data set in some public web space lets people who want the data fetch it at their leisure and doesn't cost you anything if the recipients decide they don't need it after all.