markymark31
Member
Hi Guys,
Muddling through socket communications with my EWEB as there seems to be very little information out there.
I have successfully connected and can read data sent to me (i'm the client) from the server.
I am, however, struggling to get my head around one particular part and wondered if this is how it is supposed to work or whether I am doing something not quite right ?
I thought that I could trigger a READ MSG and it would sit & wait (until the timeout value) for data to be sent to me but what is happening is that when the data comes in the MSG returns an extended error 0204 "Unconnected message timeout".
Now, using the EWEB "socket diagnositcs" web page I can see when the data comes in because the read buffer increases. With data in the buffer if I then trigger the READ MSG everything works fine and the data comes in.
Is this correct ? Does the data have to be sent before I can READ it ? I was hoping that I could trigger the READ and just sit back and wait for it !
Thanks for your help !
Mark.
Muddling through socket communications with my EWEB as there seems to be very little information out there.
I have successfully connected and can read data sent to me (i'm the client) from the server.
I am, however, struggling to get my head around one particular part and wondered if this is how it is supposed to work or whether I am doing something not quite right ?
I thought that I could trigger a READ MSG and it would sit & wait (until the timeout value) for data to be sent to me but what is happening is that when the data comes in the MSG returns an extended error 0204 "Unconnected message timeout".
Now, using the EWEB "socket diagnositcs" web page I can see when the data comes in because the read buffer increases. With data in the buffer if I then trigger the READ MSG everything works fine and the data comes in.
Is this correct ? Does the data have to be sent before I can READ it ? I was hoping that I could trigger the READ and just sit back and wait for it !
Thanks for your help !
Mark.