🚀 go-pugleaf

"David Ayre" <davidcayre@ntlworld.com> wrote in message
news:45d30c11$1@newsgroups.borland.com...

> I am using Indy 9 with BDS 2006 but have found a problem
> with the ftp module when I use IdFTP1->List(SL,"",false); If
> there is nothing in the folder it crashes.

The server is likely sending back a faulty reply.  Look at the "Indy
FTP Response Codes for NLST" discussion in the
"borland.public.delphi.internet.winsock" newsgroup from last night.


Gambit

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"David Ayre" <davidcayre@ntlworld.com> wrote in message
>news:45d30c11$1@newsgroups.borland.com...
>
>> I am using Indy 9 with BDS 2006 but have found a problem
>> with the ftp module when I use IdFTP1->List(SL,"",false); If
>> there is nothing in the folder it crashes.
>
>The server is likely sending back a faulty reply.  Look at the "Indy
>FTP Response Codes for NLST" discussion in the
>"borland.public.delphi.internet.winsock" newsgroup from last night.
>
>
>Gambit
>
>
I've had a look at the NLST discussion but couldn't glean
anything that would help me.
If the server gives the wrong response to IdFTP1->List(SL,"",false);
for an empty folder, how can I detect this and continue,
ignoring the List(), which would then be unnecessary?

David

> If the server gives the wrong response to IdFTP1->List(SL,"",false);
> for an empty folder, how can I detect this and continue,

Indy uses Exceptions therefore if a bad response is received an exception
should be thrown. That being the case you need to use try/catch to catch
the exceptions and deal with them accordingly.

If an exception isn't thrown, you should check the response code that
is returned and determine your action from there.

Regards,

Tom

"David Ayre" <davidcayre@ntlworld.com> wrote in message
news:45d430c5$1@newsgroups.borland.com...

> I've had a look at the NLST discussion but couldn't glean
> anything that would help me.

Then I suggest you use a packet sniffer, such as Ethereal, to find out
exactly what the server is sending.


Gambit

"Tom" <tom@nospam.net> wrote:
>> If the server gives the wrong response to IdFTP1->List(SL,"",false);
>> for an empty folder, how can I detect this and continue,
>
>Indy uses Exceptions therefore if a bad response is received an exception
>should be thrown. That being the case you need to use try/catch to catch
>the exceptions and deal with them accordingly.
>
>If an exception isn't thrown, you should check the response code that
>is returned and determine your action from there.
>
>Regards,
>
>Tom
>
Thanks Tom,

I thought something like that would do it, but I'm not sure how
to set it out. Could you possibly give me a code example.

Cheers,

David

David,

Without knowing the exact exception that's being thrown, I can only
give you a general try catch example. Once you get the exception
name I would only catch that exception so you can deal with any
others that may show up accordlingly.

try
{
  IdFTP1->List(SL, "", false);
}
catch (Exception &e)
{
   // This will catch every exception and handle them the same
   //  way. If you have different exceptions coming up, you need to
   // catch them separately by using the proper names.
  //  IE: catch (EIdSocketError &e) or catch (EIdProtocolReplyError)

   // If you need to do something special, put that code here.
   // otherwise the error message will disappear. Please remember
   // that the error will still be shown if you're using the debugger.
}

Regards,

Tom 

Thanks Tom,

That seems to have solved the problem.

Cheers,

David


"Tom" <tom@nospam.net> wrote:
>David,
>
>Without knowing the exact exception that's being thrown, I can only
>give you a general try catch example. Once you get the exception
>name I would only catch that exception so you can deal with any
>others that may show up accordlingly.
>
>try
>{
>  IdFTP1->List(SL, "", false);
>}
>catch (Exception &e)
>{
>   // This will catch every exception and handle them the same
>   //  way. If you have different exceptions coming up, you need to
>   // catch them separately by using the proper names.
>  //  IE: catch (EIdSocketError &e) or catch (EIdProtocolReplyError)
>
>   // If you need to do something special, put that code here.
>   // otherwise the error message will disappear. Please remember
>   // that the error will still be shown if you're using the debugger.
>}
>
>Regards,
>
>Tom 
>
>

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>"David Ayre" <davidcayre@ntlworld.com> wrote in message
>news:45d430c5$1@newsgroups.borland.com...
>
>> I've had a look at the NLST discussion but couldn't glean
>> anything that would help me.
>
>Then I suggest you use a packet sniffer, such as Ethereal, to find out
>exactly what the server is sending.
>
>
>Gambit
>
>
Thanks Remy,

Ive downloaded that and got it going. In the meantime I just put
the List() into a try/catch and allowed it to ingore the
return when there was an empty folder.
Now I can check the return and make it more specific.

Thanks for your help.

David