Re[2]: [twsocket] Receive result of the first ReceiveStr() call twice-not resolved

2005-06-02 Thread Jack
; Auteur du freeware MidWare - Multi-tiers framework > http://www.overbyte.be > - Original Message - > From: "Jack" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Thursday, June 02, 2005 12:39 AM > Subject: Re: [twsocket] Receive r

Re: [twsocket] Receive result of the first ReceiveStr() call twice-not resolved

2005-06-02 Thread Francois Piette
r du freeware MidWare - Multi-tiers framework http://www.overbyte.be - Original Message - From: "Jack" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Thursday, June 02, 2005 12:39 AM Subject: Re: [twsocket] Receive result of the first ReceiveStr() call tw

Re: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved

2005-06-01 Thread Jack
This problem is still bugging me. I did some further testing and find some strange things. In the OnDataAvailable event handler, I call the function below to get HTTP status code. The HttpReply is the string variable I get from ReceiveStr() call. I find that as long as I call this function, I get a

Re: Re[2]: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved

2005-05-21 Thread Francois PIETTE
; To: "Francois Piette" <[EMAIL PROTECTED]> Sent: Friday, May 20, 2005 10:58 PM Subject: Re[2]: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved > Hello Francois, > > Thanks for offering to look at my code. > > I zipped the (simplified) proje

Re[2]: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved

2005-05-20 Thread Jack
ti-tier framework, freeware) FP> http://www.overbyte.be FP> - Original Message - FP> From: "Jack" <[EMAIL PROTECTED]> FP> To: "ICS support mailing" FP> Sent: Thursday, May 19, 2005 9:31 PM FP> Subject: [twsocket] Receive result of the first Rece

Re: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved

2005-05-20 Thread Francois Piette
http://www.overbyte.be - Original Message - From: "Jack" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Thursday, May 19, 2005 9:31 PM Subject: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved > I celebrated a little too early. I

[twsocket] Receive result of the first ReceiveStr() call twice - not resolved

2005-05-19 Thread Jack
I celebrated a little too early. I am getting this problem again in further testing after I changed Close() to CloseDelayed(); The difference is, I'm not getting result of the first ReceiveStr() twice. Instead, I get the result of the second ReceiveStr() twice. I think this is because CloseDelayed(