Some context: the proper use of FTP is a bit of a problem in MC. I've just sent a note to andu requesting that someone create a FAQ for this problem. 'Best as I can make out, much of the problem relates to the distinction between file: and file:// where the first returns the file's data and the latter returns the file's name only. I invite clarification on this, but I've confirmed it independently.
I'm working on a project that involves sending files from Macs and Win2000 machines to a Linux server, as well as among each other. I recommend the use of an FTP server at every transmission destination; it's much easier than protocol-writing, and experience in various W3C working groups has shown that developing a robust protocol is lengthy, error-prone, and difficult on extensibility grounds. Making a protocol should be considered only when you can determine that nothing else has the slightest hope of fulfilling your needs, and with FTP (perhaps with WebDAV) I find that MC has almost everything you need, short of streaming capability. Lastly, there are *many* freeware FTP servers; on the Mac, I've used NetPresenz, on Windows just go with the built-in (and easy to configure) IIS 4 or 5. I certainly wouldn't use an HTTP server of any kind for bidirectional file transfer -- it's more complex to set up (e.g., the MIME problem), more limited on type, more prone to hack/virus attacks (e.g., are at least the many buffer-overflow scenarios anticipated?), and you would likely want/need session statefulness. The best protocol for file transfer is FTP :^) One easy method for me is to upload the file to a target FTP server, and then to request the file again (securely), running a checksum-like comparison routine to ensure that its integrity was preserved on transmission. Does this sound like a constructive possibility for your project? --- David Bovill <[EMAIL PROTECTED]> wrote: > > From: andu <[EMAIL PROTECTED]> > > Subject: Re: Writing a file remotely > > > > Gregory Lypny wrote: > >> > >> Thanks Andu and Ricardo for your advice on Mac-to-Mac file > writing > >> over TCP/IP. But how would it work, or could it work, for > WinTel users > >> with an MC stack writing to the Mac. (I think that rhymes.) > > > > I don't think AppleShare works on windows except NT server. > You may need > > to use a different protocol, the easiest probably being to > make your > > own. > > > > You could write your own protocol... it is not the route I > chose largely as > I thought the by using HTTP and hacking into Andus's MCHTTP > server script - > I'd have a more general solution. > > The way this works is to use MCHTTP to serve up binary files to > other > machines on the LAN - it needs to be altered to work with > LibUrl in 2.4 and > I am not sure how well it deals with large files - but seems > more than fine > with images, HTML and MC stacks of a reasonable size... though > it hasn't > been tested with streaming MP3 files yet -:) > > Using TCP/IP and an MC based HTTP server you can also serve up > files to > people using browsers - though it would help if they configure > their MIME > settings for MC stacks (has someone got a cross platform script > Windows - > Mac) for this. > > If you/anyone want to work on this with me - mail me off list. > > > Archives: > http://www.mail-archive.com/[email protected]/ > Info: http://www.xworlds.com/metacard/mailinglist.htm > Please send bug reports to <[EMAIL PROTECTED]>, not this list. > ===== Francisco J. Ricardo, Ph.D. __________________________________________________ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com Archives: http://www.mail-archive.com/[email protected]/ Info: http://www.xworlds.com/metacard/mailinglist.htm Please send bug reports to <[EMAIL PROTECTED]>, not this list.
