Re: [twsocket] TFtpClient - Quit never returns when not connected!

[Francois PIETTE]

 Hallo, I've a problem using TftpClient.

Is it related to the subject ? I guess no ! You should have opened a new 
thread with a proper subject.

 I can't obtain a connection, if on a Lan there is a squid proxy server.
 Why??

I can't tell you anything if you don't give more informations about the 
failed connection.
Please repost a message (do not reply to this one, create a new message) 
with subject FTP client, no connection with squid proxy and explain the 
more exactly possible what you do and what error you have. It is also useful 
to do your testing using FtpTst demo program so that we are sure it is not 
your own code which has a problem.

--
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
--
[EMAIL PROTECTED]
http://www.overbyte.be


-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Re: [twsocket] TFtpClient - Quit never returns when not connected!

[Francois PIETTE]

Not connected, quit = error code 200 (means OK)
Not connected, any other command = error code 503 or exception.

--
[EMAIL PROTECTED]
http://www.overbyte.be

- Original Message - 
From: Arno Garrels [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Saturday, January 14, 2006 8:02 PM
Subject: Re: [twsocket] TFtpClient - Quit never returns when not connected!


 Francois PIETTE wrote:
 FLastResponse  := '200 OK not connected';

 A 200 answer mean OK, let's continue.
 Probably the message should better be:
503 Bad sequence of commands. Not connected.

 As far as I understand, Quit should _not return any error when not
 connected,

 Yes, it looks reasonable for Quit command only.

 That's obviously why no longer an exception is triggered (which has been
 triggered in older versions).
 What I mean is, either an exception has to be triggered when not connected
 (I can pretty well live with that) or the command must return with an OK.
 Current handling is buggy!

 You change affect all
 commands. At test must be done to select the most appropriate error
 message given the command.

 I haven't the overview of the most appropriate error code. There should
 be an easy solution (raising an exception was easy!).


 wasn't it handled in other classes the same?

 I don't understand this. Sorry.

 As far as I recall in TSmtpCli you may call QUIT w/o raising an exception
 when not connected as well and it returns with a OK-result.


 --
 [EMAIL PROTECTED]
 http://www.overbyte.be
 -- 
 To unsubscribe or change your settings for TWSocket mailing list
 please goto http://www.elists.org/mailman/listinfo/twsocket
 Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be