Back in the olden days the server did not support UTF-8, it just sent ASCII. So as long as you knew what codepage it was using there was not a problem.
I'll see how it goes now having implemented the "Download To Stream" idea instead of "Download To String". I may well have some more questions soon on another little project based on the Overbyte FTP Server demo program. Regards Graham -----Original Message----- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Angus Robertson - Magenta Systems Ltd Sent: 08 March 2010 17:34 To: twsocket@elists.org Subject: Re: [twsocket] FPiette V2.108 vs Overbyte V7.07 - FTP Client > When I get the FEAT response, where do I look for the results? The results are parsed by the component into numerous ftpFeatxxx types so applications know whether specific features are supported. You need to log LastResponse to see them all as literals, but I'm sure your program does that for diagnostics already, otherwise you won't know the reason for commands that fail. > Although I think this is irrelevant since I have found the spec for > the server and the only FEAT supported is UTF8. In which case MLST won't work either. But some FTP servers support special SITE commands that offer alternate indexing that is better than LIST. Also, V2.108 does not support UTF8, that was not added until V7.01, this may not matter provided you never send or receive characters higher than x07F in file or directory names, but otherwise you are in trouble. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
