Merijn Bosma wrote:
> I've been using ICS for quite a while now, and a few days ago I came
> across something strange.
> One of our larger customers had some extra modules installed, causing
> a lot of more tcp clients connecting to the tcp server.
>
> Every now and then (somewhere between 1 minut
Thanks for your reply!
Arno Garrels wrote:
> You get a real infinite loop only if you called Receive() with a buffer
> size of zero.
>
Which is not the case
>
>
>> The thing is that we _always_ call ReceiveStr() in the OnDataAvailable
>> event, I think this should always read all data rece
On Apr 9, 2008, at 03:45, Bjørnar Nielsen wrote:
> The comment about the registry was there before I made any changes. My
> only change was to add 'text/xml' as content-type for extension 'xml'.
> For now my only need is this extra content-type, not another way of
> managing the list of conten
> Can anybody shed some light? :p
One possible explanation were that anytime OnDataAvailable returns,
just a few _new_ bytes are available in winsock buffer. Could be
possible due to the background thread winsock creates internally
with non-blocking sockets, though I'm not aware of how winsock wo
Merijn Bosma wrote:
> again, I'm still coming to the same conclusion: either bug in
> ReceiveStr(), bug in handling of wsoNoReceiveLoop,
Again I don't agree because as you described it works as
documented. Quoted from the unit comment section:
"Added ComponentOptions property with currently only
I'll reply to both your mails in a single one:
> One possible explanation were that anytime OnDataAvailable returns,
> just a few _new_ bytes are available in winsock buffer. Could be
> possible due to the background thread winsock creates internally
> with non-blocking sockets, though I'm not aw
>> One possible explanation were that anytime OnDataAvailable returns,
>> just a few _new_ bytes are available in winsock buffer. Could be
>> possible due to the background thread winsock creates internally
>> with non-blocking sockets, though I'm not aware of how winsock works
>> under the hood.
>
Francois PIETTE wrote:
>>> One possible explanation were that anytime OnDataAvailable returns,
>>> just a few _new_ bytes are available in winsock buffer. Could be
>>> possible due to the background thread winsock creates internally
>>> with non-blocking sockets, though I'm not aware of how winsock
