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
Hello John,
> I seem to get the OnDataSent event when I initially connect to a socket and
> before sending any data - is this correct?
Yes this is correct. There is data deliverd to initiate the connection,
so winsock generates this event.
> I am confused as to what the ReadCount is
Where is th
>I seem to get the OnDataSent event when I initially connect to a socket and
> before sending any data - is this correct?
Yes. OnDataSent is triggered when all data has been sent /and/ at the start
of connection when the component is ready to send something.
> I am confused as to what the ReadCo
I seem to get the OnDataSent event when I initially connect to a socket and
before sending any data - is this correct?
I am confused as to what the ReadCount is. Is it simply a sum of all the
bytes which have been read by the Received method since the session was
started or is the number of byte
> > Not exacly. OnDataSent is fired when TWSocket has empty his buffer. But
> > you are right about when it is emptied between the calls, but of course
> > only when messages are processed.
>
> So if Winsock buffer is NOT emptied, but TWSocket is, the event is fired
> anyway?
Yes indeed.OnDataSent
Hello!
> Not exacly. OnDataSent is fired when TWSocket has empty his buffer. But
> you are right about when it is emptied between the calls, but of course
> only when messages are processed.
So if Winsock buffer is NOT emptied, but TWSocket is, the event is fired
anyway?
--
Piotr "Hellrayzer"
Hello Jack,
Not exacly. OnDataSent is fired when TWSocket has empty his buffer. But
you are right about when it is emptied between the calls, but of course
only when messages are processed.
---
Rgds, Wilfried
http://www.mestdagh.biz
Tuesday, March 15, 2005, 00:11, Jack wrote:
> Hello Francois a
Hello Francois and all,
I have a question about the OnDataSent event. When is
OnDataSent is fired? Is it fired when the data buffer
of the TCP stack is emptied? If so, after calling the
Send or SendStr function a few times, I suppose I could
get OnDataSent event one or more times depending on
whet
13 matches
Mail list logo
