Firstly, why SSH/FTP/email? Due primarily to heavy use, HTTP is now an extremely effective single-file transfer method, with download managers etc that can handle interrupted connections in a fashion that SSH and, to a lesser extent FTP, still struggle with. Lets not even talk about email for moving large files. (how large is large?)
Secondly, the solution to your cost question is obvious, assuming no unstated limitations: host the site in the US or EU where they have sane bandwidth prices. Regards, Richard. On 22 April 2010 20:22, .Net2Php <[email protected]> wrote: > I need some suggestions on how to effectively manage bandwidth to and > from servers. > > Large files need to be transferred from client computer to a website > AND from website back to client. This transferring will be done via: > FTP, SSH and email. The website can be configured so that the client > can provide FTP or SSH account details to his/her server; this will > allow the website to access the client's server and retrieve the large > documents. Alternatively, the website can provide FTP and SSH account > details to the client so that the client can send the large files a > server accessible to the website. Same basic idea also applies for the > email sending/receiving. > > The problem is bandwidth cost. If the client is in NZ and the server > (FTP, SSH, email) is in NZ, then there is no bandwidth cost (other > than nominal costs). However, if the client is outside of NZ, it > becomes expensive to retrieve these files. > > Clients can be anywhere in the world. Website will need access to > those large files no matter where they reside. > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
