> to my problem I found something out: if I disable processing of these
> commands up to 100.000 and more are stored in the queue, so the sending
> and receiving of them via ICS works well.
:-)
> The receiving uses a tight loop to extract all commands out of the
> ringbuffer and stores them in t
Hello,
to my problem I found something out: if I disable processing of these
commands up to 100.000 and more are stored in the queue, so the sending
and receiving of them via ICS works well.
The receiving uses a tight loop to extract all commands out of the
ringbuffer and stores them in the queue
PROTECTED] On
Behalf Of Markus Humm
Sent: 14 September 2006 21:54
To: ICS support mailing
Subject: [twsocket] complex problem, probably not ICS related
Hello,
sorry, this will be just a tiny bit longer... ;-)
I'm currently building some large application where several parts will
act together. T
ling"
Sent: Thursday, September 14, 2006 10:53 PM
Subject: [twsocket] complex problem, probably not ICS related
> Hello,
>
> sorry, this will be just a tiny bit longer... ;-)
>
> I'm currently building some large application where several parts will
> act together. Two of
Hello,
sorry, this will be just a tiny bit longer... ;-)
I'm currently building some large application where several parts will
act together. Two of them are connected via TCP and TWSocket. One is
client and one server (okay there is TWSocketServer, but since there's
always a 1:1 relation between
