Fastream Technologies wrote:
> Hello,
>
> In some cases SetReady() (hence OnRequestDone) is called twice, where
> the second one should not be called and interferes with following
> HTTP request (if any), ruining the state machine. I suggest something
> like:
>
> void __fastcall SetReady()
> {
> if(alreadySetReady)
> return;
> alreadySetReady = true;
> ...
> }
> //---------------------------------------------------------------------------
Such a fix won't fix the cause of the problem.
Also don't you use a custom OverbyteIcsHttpProt.pas?
This fix from SVN rev. #623 springs to mind:
procedure THttpCli.Abort;
var
bFlag : Boolean;
Msg : TMessage;
begin
FLocationFlag := FALSE; { Do not follow relocations V7.10 }
{ The following two lines prevent OnRequestDone from trigger twice V7.10 }
FRcvdCount := 0; { Clear the receive buffer V7.10 }
FReceiveLen := 0; { Clear the receive buffer V7.10 }
[..]
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
