>Well, we'll have to somehow determine local code errors then
I meant, "local errors' codes"
--
Anton
--
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
Hello Francois, hope you liked your trip :)
>Arno's suggestion looks good and wouldn't break any existing code.
Well, we'll have to somehow determine local code errors then. And not forget to
clear the flag. But at least it will provide a way to deal with the problem.
>As far as I remember, you
AS>> > Current manner of reporting local errors is to set code 550 with an
explaining message
AS>>> and call TriggerRequestDone. But I find it very confusing: for
example, when trying to
AS>>> GET some file or directory listing we could receive "true FTP
response" 550 if the
AS>>> requested fi
So, what will be your decision?
I wouldn't hurry you, but I have a buggy project based on old FTP components
and wish to rebuild it with ICS.
Looking forward to your answer.
--
Anton
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/ma
>Have you tried calling GetLastError or WSAGetLastError ?
I think it's unreliable because error can occur by exception not by Winsock or
Windows error. Moreover, LastError-s could be overwritten by subsequent API
calls by the moment OnRequestDone will be called.
--
Anton
--
To unsubscribe or ch
To:
Sent: Thursday, April 29, 2010 2:20 PM
Subject: [twsocket] FTPCli error handling
Hello all,
it's me again and again with a question about FTPCli.
Current manner of reporting local errors is to set code 550 with an
explaining message and call TriggerRequestDone. But I find it very
confusi
Hello Arno,
>If a workaround is needed then IMO a field "FLastLocalError" of type
>LongWord or Integer could receive a meaningful error code and a method
>GetLastLocalError could return and reset the value back to 0?
Well, it's something. Though I'm still not sure what's the best way to deal
w
Anton Sviridov wrote:
> unconvenient). So I think something is needed to be done to
> differentiate local problems of remote ones. I'd prefer changing 550
> code to some another value unused by FTP servers (maybe even over 600
> to avoid intersections for sure).
> but the ICS policy is NOT BREAK
Hello all,
it's me again and again with a question about FTPCli.
Current manner of reporting local errors is to set code 550 with an explaining
message and call TriggerRequestDone. But I find it very confusing: for example,
when trying to GET some file or directory listing we could receive "true
