socket write/read conflict?

Len Morgan len-morgan at crcom.net
Tue Mar 23 00:05:09 EDT 2010


Two things jumped out at me in your code:
1) broadcastToAllClients - you show an IP address of 127.0.0.1.  If this 
was not just an example, you can't use that number.  That is the IP of 
the local host and won't actually ever leave the machine.

2) You are selecting item 3 of tArrayDataLine which I assume is comma 
delimited (based on the example line above it).  I don't set a 
"setItemDelimiter to comma" in that handler and I /think /the default 
delimiter is tab.  I also believe that the itemDelimiter you set is only 
valid for the current handler so as soon as this handler is finished, it 
will revert back to tab.

Hope that helps a little.

len


On 3/22/2010 10:14 PM, Nicolas Cueto wrote:
> Hello List,
>
> I've made a quiz-type game where 2-6 students on client stacks buzz in
> their answers to a server stack, all on a local network. The server
> stack, as well as sending out the questions, informs live to all the
> students/client-stacks about who buzzed in what.
>
> I thought I had it working until we found a problem. If two out of six
> students happen to buzz in an answer almost simultaneously (by
> clicking a button on a game controller pad), as expected five of the
> students will receive the server's message about who buzzed in first,
> but one of those two students who buzzed at the same time won't.
> Except for this simultaneity, all other server-to-client
> communications work.
>
> After trying to track this down for weeks, I'm posting here in hopes
> of some list magic.
>
> My guess, as the subject line reads, is that a client stack might be
> writing to a socket at the same time that the server is trying to
> write to that same socket. But, not understanding well how sockets
> work, the problem may lie elsewhere. I think I've eliminated the
> obvious types of mistakes, but...
>
> So, I am including below the essence of what my server and script
> stacks do. It is quite long, so apologies beforehand.
>
> As always, the list's help in this is greatly appreciated.
>
> Thank you.
>
> -- Nicolas Cueto
>
>    




More information about the use-livecode mailing list