LiveCode Forums.

Hi, folks.

Thanks in advance for any possible help.

Without using sockets, can URL "get" a file from another computer on the same router? There is not actually a server involved, nor an outside www. address. What would the syntax be?

For example, REV on machine 127.0.0.1, router IP of 192.168.1.100, wants to get file "c:test.txt" from machine 192.168.1.101 on same router. Is there a form of "http" or "ftp" that would work?

Thanks for any ideas.

Rev doesn't care what IP it's being asked to use. I've used local addresses without difficulty. What happened when you tried it?

Hi Ken,

http works on a web server so you need to have the file in the web hierarchy and have the server running then this will get it.

get URL "http://192.168.1.101/test.txt"

If you want to use ftp you similarly have to have an ftp server running and have the file in an ftp accessible directory.

get URL "ftp://192.168.1.101/test.txt"

I don't think that RunRev uses sfs (Windows simple file sharing) or afp (the Apple equivalent) so I suspect that unless you have a server running you will not be able to access a file on another machine on the same router.

I realise that this may not answer your question but at least it might help you narrow things down.

Cheers

Phil

Thanks, Richard & Phil,

Yes, if the target machine has a server running, things work fine to use either of the approaches mentioned.

My hope was that some faster file sharing (without a server connection) might be possible. For this particular application, the objective is to move a data file from a RAM drive on 1 machine, directly into a REV field app on the other.

Thanks for your input.

Is there some reason you don't want to use sockets for this? That seems to fit the bill perfectly for what you want to do, and you'd be hard-pressed to find anything faster.

Sounds more like he's looking at network shares here which using http will not work with. It will require network paths instead of internet paths, provided the other machine has a network share open.

I believe this would be the proper way here:

get URL "\\johndoe-desktop\sharedfiles\test.txt"

But I'm honestly not sure this is correct or not as I have not done any network coding with Rev.

Thanks for the ideas.

I had originally intended to use sockets, but was not sure about "sending" a message that was so large -- the file size might be an issue. And that would involve running another REV socket program on the file side to use for the send.

However, since file sharing may work, let me test both approaches on the large files and see how it goes.

I'll post back once the better solution is confirmed.

Thanks again.

Thanks to all who made suggestions.

The better solution seems to be using sockets to send and receive the data files.

Size of the data files did not prove to be an issue, and the transfers work seamlessly. Running "tiny" REV programs to handle the socket communications is simpler than "network shared files" and faster than http or ftp with a server.

Regards,