Hi,
I have been using the ftp client component for a couple of years now
without a hitch. Until recently. The version is 7.09.
I have in the main thread a timer that runs a state machine to control
logging in and sending of the files. But recently, the state machine
stalls and times out. I h
Info2004 wrote:
>> PASV
> < 227 Entering Passive Mode (65,212,180,79,238,1)
> ! Upload Size 91
>> STOR 17012012_1319010_leeEcersley.csv
>
I guess the server did not send a response to the STOR
request after the client successfully established the data
connection. Since this is async mode your ap
Hi,
i am using the Standard TWSocket in a Server and round about 5 Clients without
LineMode. After a Client is connected to the Server, the Client starts
immediately to send text messages. After some sort of filtering the messages
are broadcasted to a subset of all connected Clients. If i start th
> If the ClientSocket is closed, the callback for OnDataAvailable is
> triggered and the missing Bytes are "received".
This is the common sympton of missing line endings so the event is never
called. But this would not explain why it's suddenly happening.
I gave up on LineMode a long time ago,
I had a similar problem when converting to XE2 from Delphi7 - my TwSocket
component was designed to send a header string containing the length of the
data to follow, and then I would read that bit to get the actual data - and
then process it - but with XE2 being unicode aware - suddenly I had extra
probably your backend ftp server has been changed to 'binary' type - and
when receiving your request to STOR the .csv file - it is issuing a type A
to change the mode to ASCII
You could force the Type A before issuing your STOR.
Regards
Brian
On Wed, Feb 1, 2012 at 2:43 AM, Info2004 wrote:
> H
On 31/01/2012 17:41, Arno Garrels wrote:
I guess the server did not send a response to the STOR
request after the client successfully established the data
connection. Since this is async mode your application
should have detected and handled a request timeout.
Arno,
What is the correct way to
On 31/01/2012 19:05, Brian Culverwell wrote:
probably your backend ftp server has been changed to 'binary' type - and
when receiving your request to STOR the .csv file - it is issuing a type A
to change the mode to ASCII
You could force the Type A before issuing your STOR.
Brian,
Do you mean
I think I have understood little or nothing.
We summarize. I have to read e-mail. I read the first post and everything is ok
(they are executed properly onheaderend events, onmessageend, ...
Step to read any other message (which exists) is not getting any error message
but still displays the info
> We summarize. I have to read e-mail. I read the first post and everything
is ok (they
> are executed properly onheaderend events, onmessageend, ...
> Step to read any other message (which exists) is not getting any error
message but
> still displays the information of the first message and even
Imposed on the host, user, password, etc.. I run in order opensync, statsync,
listsync, uidlsync, and retrsync quitsync.
It 's always the same procedure only changes the value of msgnum course.
When you start running with msgnum = 1 is ok. Any value set does not produce
results, and then I notice
before each STOR
On Wed, Feb 1, 2012 at 6:27 AM, Info2004 wrote:
> On 31/01/2012 19:05, Brian Culverwell wrote:
>
>> probably your backend ftp server has been changed to 'binary' type - and
>> when receiving your request to STOR the .csv file - it is issuing a type A
>> to change the mode to ASC
OK.
Thanks.
On 31/01/2012 21:46, Brian Culverwell wrote:
before each STOR
On Wed, Feb 1, 2012 at 6:27 AM, Info2004 wrote:
On 31/01/2012 19:05, Brian Culverwell wrote:
probably your backend ftp server has been changed to 'binary' type - and
when receiving your request to STOR the .csv file
Info2004 wrote:
> On 31/01/2012 17:41, Arno Garrels wrote:
>>
>> I guess the server did not send a response to the STOR
>> request after the client successfully established the data
>> connection. Since this is async mode your application
>> should have detected and handled a request timeout.
>>
Brian Culverwell wrote:
> probably your backend ftp server has been changed to 'binary' type -
> and when receiving your request to STOR the .csv file - it is issuing
> a type A to change the mode to ASCII
A server doesn't issue commands, regardless of which type is active
the upload should basica
15 matches
Mail list logo
