Hi Wilfried
But it will break existing code that depents on this behaviour if
wsoNoReceiveLoop is set. But you can easely derive from TWSocket and
override do_fd_close method. Then it will behave good for your
specifications and you will never have to change code again after updates.
I see you
Hi Eric,
> I know, but if you still call OnDataAvailable with current socket
> options,
> for the ones that has not set wsoNoReceiveLoop (By default) the
> behaviour
> will still be the same right... for the ones that has set
> wsoNoReceiveLoop
> (like me) OnDataAvailable will still be called, and
Never done somthing like that, I guess you have to ensure that data is
processed in the right order with such a design, as with Windows IOCP
sockets as well.
No problem here, I have a worker thread system, the data will always be
processed in right order
Yes, I understand, but there's a re
> I know this is by design, but I believe that is why you have added
> wsoNoReceiveLoop so we don´t have to receive data in OnDataAvailable...
No this is addes to get out of a closed loop in case of users had slow code
to process fast data.
> software wasn´t being able to process over 150mbits of
Éric Fleming Bonilha wrote:
> Arno
>
> I use multiple threads to read the data from sockets, I actually have
> a thread pool that process data.
Never done somthing like that, I guess you have to ensure that data is
processed in the right order with such a design, as with Windows IOCP
sockets as w
Arno
I use multiple threads to read the data from sockets, I actually have a
thread pool that process data.
This is my current code for OnDataAvailable from sockets:
procedure TTCPSocketThread.HandleOnSocketDataAvailable(Sender: TObject;
ErrCode: Word);
begin
// We can´t proceed on errors
Arno Garrels wrote:
> Éric Fleming Bonilha wrote:
>> I know this is by design, but I believe that is why you have added
>> wsoNoReceiveLoop so we don´t have to receive data in
>> OnDataAvailable...
>>
>> By reading the socket using OnDataAvailable event I reached a
>> bottleneck, my software wasn´
Éric Fleming Bonilha wrote:
> I know this is by design, but I believe that is why you have added
> wsoNoReceiveLoop so we don´t have to receive data in
> OnDataAvailable...
>
> By reading the socket using OnDataAvailable event I reached a
> bottleneck, my software wasn´t being able to process ove
I know this is by design, but I believe that is why you have added
wsoNoReceiveLoop so we don´t have to receive data in OnDataAvailable...
By reading the socket using OnDataAvailable event I reached a bottleneck, my
software wasn´t being able to process over 150mbits of incomming data
because
Hi,
> it is expecting that my
> event handler DO receive the data (But it doesn´t) and then, it locks
> up on a loop!
You have to receive the available data in the OnDataAvailable event handler.
This is by design. If you want to process the data in another thread then
the most obvious is that you
Hi
I believe I found a showstopper bug in ICS that lead my software to crash in
many customers.
The problem is with wsoNoReceiveLoop option from socket!
In my program, I have to use wsoNoReceiveLoop in order to better process the
data, I don´t want to process the data from the thread that fire
11 matches
Mail list logo
