Thanks guys.
Regards,
Andy
Wilfried Mestdagh wrote:
> Hello Andy,
>
>> I think that we are at cross purposes here. The OnDataSent event looks like
>> it
>> does not fire (sometimes) if the far end (server) closes the connection. Is
>> this
>> true?
>
> OnDataSent is fired when TWSocket has de
Hello Andy,
> I think that we are at cross purposes here. The OnDataSent event looks like it
> does not fire (sometimes) if the far end (server) closes the connection. Is
> this
> true?
OnDataSent is fired when TWSocket has delivered his data to winsock. As
Arno pointed out it is not a signal th
info2004 wrote:
> Arno,
> Arno Garrels wrote:
>> info2004 wrote:
>> When the server closes the connection OnSessionClosed triggers.
>> In order to check whether component's internal send buffer is empty
>> you have property BufferedByteCount.
>>
>> If your application has to close the connection w
Arno,
Arno Garrels wrote:
> info2004 wrote:
> When the server closes the connection OnSessionClosed triggers.
> In order to check whether component's internal send buffer is empty
> you have property BufferedByteCount.
>
> If your application has to close the connection when all data
> has been s
info2004 wrote:
> Hi,
>
> I am currently using the OnDataSent event of TWSocket to signal my
> state machine to move on. This is working mostly, however, sometimes,
> the event does not happen.
>
> Now, at the far side, the server being connected to closes the
> connection when
> it has it's da
Hi,
I am currently using the OnDataSent event of TWSocket to signal my state
machine
to move on. This is working mostly, however, sometimes, the event does not
happen.
Now, at the far side, the server being connected to closes the connection when
it has it's data, so I am thinking that this c
