Hello,
I am suspcious about:
{* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*}
{ Triggered when socket is closed. Need to inform server socket to
date }
{ client list and trigger client disconnect
}
procedure TWSocketMTClient.TriggerSessionClosed(ErrCode :
I've been able to reproduce the problem and to fix it !
The bug is in OverbyteIcsWSockBuf.pas. In function TBuffer.Write, you'll
find a line:
Move(Data^, (PChar(Buf) + WrCount)^, Copied);
which must be replaced by this one:
Move((PChar(Data) + Offset)^, (PChar(Buf) + WrCount)^, Cop
A critical bug has been fixed in the ICS-V6 beta (see messages "ICS V6 Http
Post problem").
When send more than 1460 bytes in a single Send or SendStr, data was
corrupted.
The fixed zip file is available for download as usual.
btw: This version has NNTP component added (no demo yet) as well as t
Does this fix also needed for v5?
Regards,
SZ
- Original Message -
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To:
Sent: Saturday, March 25, 2006 11:25 AM
Subject: [twsocket] ICS-V6 beta fixed, NNTP added.
>A critical bug has been fixed in the ICS-V6 beta (see messages "ICS V6 Http
>
> Does this fix also needed for v5?
No need. It was an error introduced when converting the code from V5 to V6.
--
[EMAIL PROTECTED]
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our
Hello,
It is just a demo how you can do things. It make for example no error
checking, no checking on duplicate file names etc. If you want to send
files one by one, you just change in the protocol that the server say to
the client 'you can send now' (by way of a command). After receiving
that com
THIS WAS A BORLAND COMPILER BUG!!!
IF YOU ARE USING C++ BUILDER READ CAREFULLY:
There is only one operator in C++ that takes three arguments (as you
probably already know):
condition ? if_true_do_this : if_false_do_this.
The bug occurs in nested cases:
condition1 ? (condition2 ? if2true : if2
Hello,
now as I have sokme time to visit my dll problem again I recoded the
whole thing according to your suggestions which I do appreciate.
But it nevertheless crashes, although not as often as before. A TeabB
member already told me that I shouldn't create and destroy my global dll
thread I'm us
> Now I wrote a simple test program which Loadlibraries the dll, waits
> some ms and freelibraries it then and waits another few ms. This is done
> up to 1000 times to check whether it works or not. if only done a few
> times all is well, but when really trying to do it 1000x it crashes (the
> app
