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

2005-06-02 Thread Jack
: Jack [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, June 02, 2005 12:39 AM Subject: Re: [twsocket] Receive result of the first ReceiveStr() call twice-not resolved This problem is still bugging me. I did some further testing and find some strange things

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

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

2005-05-20 Thread Francois Piette
://www.overbyte.be - Original Message - From: Jack [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org 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 am getting this problem

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

2005-05-20 Thread Jack
Message - FP From: Jack [EMAIL PROTECTED] FP To: ICS support mailing twsocket@elists.org FP Sent: Thursday, May 19, 2005 9:31 PM FP Subject: [twsocket] Receive result of the first ReceiveStr() call twice -not resolved I celebrated a little too early. I am getting this problem again in further

[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