If this is all you want to do, then it may be of use to you. I only tested this on a single file, and I know next to nothing about internet protocols, but it looked neat and tidy, so I decided to try it for myself.
I've often thought just how nice it would be if files, web pages, email and even newsgroups could be read, uploaded and downloaded over the net that easily.
When reading, the OPEN downloads the file and could throw a File Not Found or other error and then reading could come from a temporary file. Writing would be to a temporary file and on CLOSE the upload would automatically happen, and throw errors then if it fails.
I think there is an argument to be able to overload or vector OPEN and CLOSE to allow such things to be done, and while I can see the reasoning for FB having moved from OPEN "COM1:..." to OPEN COM etc, I'd much prefer to see a language which allowed the file spec to determine what needs to be done.
The argument against is that massive runtime support has to be included in an executable which more often than not isn't needed. I'm sure there would be a way to allow the user to specify what runtime support was included at compile/link time and the availability of runtime support could be checked when OPEN etc is called with minimal overhead. That would give the best of both worlds.
Open "INET:http://www.google.com" For binary As #1
Open an internet site. I tried hacking in an rtlib module for "OPEN TCP", but I cancel'd it because sending and receiving through FB's virtual file system would make the other end reset the connection all the time.
See the example file "openhook.bas" that comes with FB for a quick rundown on how to hook the OPEN command, if you wish to implement this yourself.
Hippy: I was surprised too. Unlike most basic compilers, FB gives you the ability not commonly used in the basic world. The ability to play around with it's functions, and macroing and such helps too.
You can basically take what Fb has and manipulate it to your own advantage.