Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

[REBOL] Re: Reading empty directories via FTP error

From: brett:codeconscious at: 14-Nov-2003 10:10

Hi Romano,
> another problem of the ftp handler is error handling (see > http://www.rebol.net/list/list-msgs/32024.html)
I see your point about the error handling code in the FTP protocol - it does not look robust to me. As I understand it, Catch does not trap errors at all, yet the FTP protocol code has "error? catch" in multiple places through the code. As users we can wrap our FTP stuff in a Try or Attempt to protect ourselves, but still the FTP code may fall apart unreasonably early.
> > I tried briefly to replicate the problem but couldn't - I got a
different
> > error! > > What error?
I think the FTP server was complaining about the directory not existing - I haven't traced the problem, but I did find that at some point I couldn't then do previously working commands.
> My error manifests itself only under some conditions (i am not able to say > exactly what conditions). I think that they depend from cached ftp port,
but i
> am not sure. With a freshly opened shell and new ftp port it should not > happen.
Ok.
> I think that the initial Ashley error with empty dirs was due to a not > existing dir + cached ftp port.
Ashley's 226 error was solved (see patch in REBOL library). Ashley also had the same error as Carl's (NLST) - which hopefully now is solved. Ashley's third problem was a general one about having had an FTP error, FTP could become unusable for the rest of the session - which I think you have identified in your error handling comments. Regards, Brett.