LiveCode Forums.

If I understand the accept command right, it opens a new socket. The way I use sockets is to keep them open until the application is finished and not opening an new one for each message to be sent. But your code seems to do that, right? Although I already tried this before, I added "until return" to...

-you open the socket -a callback message is fired, once the connexion is made -then read the data until a special character is read (here : "#") -then when read is completed (condition of the until "#" is being met), a second message is fired -the second call back message allow you to process the d...

You should try my solution : one message to be fired when data arrive, and another message once the reading is done. I'm not positive it would solve your problem. But before I've encountered this issue of reading the same data, several times. With the structure I describe, it solved this issue (plu...

I'm not sure what you mean by differentiate. I don't see why the script would be called twice as the message is supposed to be erased from the socket after reading. Or maybe that assumption is the reason why I do have such problems indentifying the cause of this. Anyway, as I understand the read fro...

Thanks for your reply. I tried adding the wait for messages and it improved things but sometimes the message is still read twice.

I cannot close the socket because I have to check continuesly for new messages which have to be handled. Any other opinions on this topic?

Hi everyone, I have a bit of a strange problem and I first have to say that I am not 100 % sure if it is runRev related at all. But anyway, here is what I'm doing: I have a socket connection with runRev as the server and an application written in C++ as the client, using my own protocol. Everything ...