<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12"> <TITLE>RE: [JDEV] File transfers</TITLE> </HEAD> <BODY> Max writes to Mike: > Have you been looking at the fact that no service provider is > going to be able to afford a system that does in-band binary > transfer exclusively?  Are you saying all file transfer and > binary data (H.323) belong in band?  Just trying to make sure > I understand your suggestion. I could be wrong, but I suspect Mike's target environment is the corporate LAN and the big box, where bandwidth and storage concerns matter less, and users may be sharing files to many users simultaneously. Only pragmatic experiment can tell, but I suspect in an Internet environment (bandwidth is metered and relatively low, servers are relatively underpowered, users tend to share files 1 to 1 'at once' rather than 1 to many 'at once'), server-based file serving is not going to work out that well. The only way to know is to try it.  And, no matter what, someone somewhere is going to do that, so Mike might as well write up what the best available technique is, maybe implement it, see what happens.  When I ran the figures, I could run ~1000 messaging users on my jabberd for about $30/month.  If those users each traded 1 5M mp3/day, my server would be averaging about 10M * 1000 = 10G of transfer extra a day = $2700/month.  Perhaps a bit much. My cost if they use straight peer-peer connections: $30/month. F. <CODE> ********************************************************************** E-mail sent through the Internet is not secure. Western Asset therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Western Asset therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. ********************************************************************** </CODE> </BODY> </HTML>