That's useful but it requires that the recipient have a server
installed.
No, that's only the sender's link, only for you to upload to
a server under your control, could even be on your present
system. You provide the recipient with a simple link... and
sometimes an HTTP link is more compatible for windows users
than FTP, so the link they'd use to get the file could look
similar to anything you'd find on a webpage, like,
http://IP#/path/file.zip
You don't have to care what their system has set as the
default handler for this, if they can download anything at
all and you have provided a typographically correct link,
they can get it without you caring or explaining anything.
For example,
"Hey Bob, here's that router picture you wanted:
http://69.36.189.159:80/usr_1034/WHR-HP-G54/bobisnuts.jpg "
However I uploaded it, doesn't matter to the recipient, they
only need a link to it using a protocol their system
supports.
That's useful but it requires that the recipient have Yahoo messenger
installed.
No, as with the above bobisnuts example, the recipient's
system will have a default handler for HTTP already if it
had remotely modern internet capabilities at all.
If I wanted to send you a large file and I knew your IP address, then
how would I do it quickly?
P2P. Software installed at both ends, more of a hassle than
it's worth for occasional use and requires a heck of a lot
more than 2 clicks per side, including easing of security,
routing issues, troubleshooting if the recipient (or sender)
didn't have it set up right.
Assume you are a typical user who has no
servers running (or even more typical, your ISP blocks low number
incoming ports so you have to configure the transfer to a high number
port).
That doesn't really change anything of consequence,
bobisnuts:
http://69.36.189.159:80/usr_1034/WHR-HP-G54/bobisnuts.jpg
http://IP#:port#/path/file.zip
Pick a port, that your ISP doesn't block and there you
are... put it in the link and send link to recipient.
My son found this utility which we have not had the chance to try out:
http://www.whitsoftdev.com/ssft/
It's apparently not official FTP but I don't care as long as it is
easy for anyone to use. However it does require poking a hole in NAT,
and most people do not know how to do that.
It may also require reconfiguring Windows Firewall, and
could be fighting against Windows Vista, considered
Trojan-like by antivirus scanners not aware of it. That
doesn't necessarily make it unworkable but only you can
assess the capabilities of the recipient. IMO, if you can
get them to do it with a web browser, so much the better as
even devices like some mobile *phones* may be able to get
the file then.
It is beginning to look like the best way to send a large file is with
one of the messenger utilities. At least they are easy to set up and
do not require poking holes in NAT.
They won't? First if you have a box sitting directly on the
internet running windows messenger, you may be quite quickly
bombared by messenger spam. Second, unless you are sending
and receiving on the box doing the NAT, yes there has to be
a "hole". Remember that what appears to work for you might
not always work for others. Maybe that doesn't matter, if
your recipient can get the file... or maybe they can't.
