Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-17 Thread Dan
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of [EMAIL PROTECTED] > Sent: 17 January 2007 22:12 > To: twsocket@elists.org > Subject: Re: [twsocket] WinSock error 10035 with TWSocketServer > > Hi Dan, > >

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-17 Thread bevan
Hi Dan, > > > TWSocketClient* Client = dynamic_cast(Sender); > > > AnsiString msg = Client->ReceiveStr(); > > > > The first line will execute, I think the second line will generate an > > exception here. I´m not sure. Did you have it into an exception block ? > > > > As far as I know the dynam

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-17 Thread Dan
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Wilfried Mestdagh > Sent: 13 January 2007 17:07 > To: twsocket@elists.org > Subject: Re: [twsocket] WinSock error 10035 with TWSocketServer > > Hello Bevan, > > I&

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-13 Thread Wilfried Mestdagh
Hello Bevan, I'm not a CBuilder specialis but: > AnsiString msg = ((TWSocketClient*) Sender)->ReceiveStr(); This is a good typecast. It tells the compiler that Sender is of type TWSocketClient, so compiler can do the exact address offset calculations within the type. You still have to check if

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-12 Thread bevan
Hi Wilfried, > It is normal that you receive an empty string once a while. Just exit > the OnDataAvailable event in that case. When data is really ready to > receive OnDataAvailable will fire again. I see your point - the other day I got the same result over and over again, today the same code w

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-12 Thread Wilfried Mestdagh
Hello Bevan, It is normal that you receive an empty string once a while. Just exit the OnDataAvailable event in that case. When data is really ready to receive OnDataAvailable will fire again. About the 10035 yo dont have to worry. This is internally handled by TWSocket. --- Rgds, Wilfried [Team

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-11 Thread Bevan Edwards
Hi Francois, Thanks for your prompt reply. >> I'm getting error 10035 (operation would block) and >> wondered why this would happen now and not >> previously. > > Error 10035 is not really an error when using non blocking socket. It just > means nothing is ready to be read. > Instead of Receiv

Re: [twsocket] WinSock error 10035 with TWSocketServer

2007-01-11 Thread Francois PIETTE
> resulting in an empty string, despite the fact that by inspecting the > object I could see there is data in the receive buffer. There is no receive buffer in the component ! > I'm getting error 10035 (operation would block) and > wondered why this would happen now and not > previously. Error