[REBOL] Re: Reading empty directories via FTP error
From: maximo:meteorstudios at: 11-Nov-2003 11:20
sorry for butting in late, but as mentioned in another mail, I have not followed the
list for a few days... hope I am not repeating past information.
> -----Original Message-----
> From: Gregg Irwin [mailto:[greggirwin--mindspring--com]]
> Sent: Tuesday, November 11, 2003 10:51 AM
> To: Ashley Trüter
> Subject: [REBOL] Re: Reading empty directories via FTP error
> Hi Ashley,
> AT> but I am finding the whole REBOL ftp thing a bit flaky
> (empty dirs or not)
> AT> with various port errors cropping up at weird places
> (almost like once a
> AT> port error occurs then all downstream operations are
> impacted). Need to
> AT> look at this a bit more before giving up on the whole
> excercise (trying to
> AT> do a simple FTP sync script in REBOL that actually works).
> I think the FTP protocol is part of the problem, and different
> implementations may be another part. I seem to recall Reichart saying
> that getting the FTP stuff robust in FTPGadget was their biggest
> issue, but not because of REBOL.
I've basically had the same kind of server-centric ugly reactions. Doing file sync engine
is easy in theory, but when each ftp server replies at his own whim, its hard to make
all features symmetric on any server...
the RFC for ftp is filled with nasties about different implementations and its apparent
by reading it that too many people "contributed" to it over such a long period of time.
for example on some servers, creating directories does not map to the same paths as creating
files ... because the web root and site root do not map the same with files and directories...
what a shit load of fun. BUT if you find the magical url base path, you eventually find
something that sort of works, but not always, again a head splitter.
finally, opening the ftp port with open() and running another function (I don't recall
which one, Gregg will ;-), worked well for my issues, because open forces the path in
a way that you are sure the path you are opening is based on your site root and not the
If you're really just doing stuff for your site/workgroup... iron out the issues with
your server and then you'll be happy, cause once you understand its quirks, ftp **UPLOADING**
becomes easy (cause D/L is always a snap).
You can either be part of the problem or part of the solution, but in the end, being
part of the problem is much more fun.