Re: sockets - opening and closing
Did you try in adding the line below to your preopenstack script : set the socketTimeoutInterval to 10 thanks for the tip, i'll give it a try in the next revision of my project ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: sockets - opening and closing
Hi Although not directly relevant to the problems discussed, it's probably a good idea to check the result after an open socket statement. It seems that if the connection fails to open due to a name resolution problem, the error is found in the result, not a socketError message. Cheers Dave Cragg ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
sockets - opening and closing
i've noticed that when creating a TCP socket that opening and closing it a few times in a row causes it not to work anymore.. open close open -- stops here most of the time if you wait a little between the first close and the second open, it will sometimes re-connect.. anyone else notice this, or am i the only one hammering? ;-) [this feature was noticed in my code as well as the 'simple server/client' available for download on the runrev website] running - windows 2000 sp2 another user has seen the same problem on macos9 ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: sockets - opening and closing
On Friday, May 3, 2002, at 07:18 PM, Shao Sean wrote: i've noticed that when creating a TCP socket that opening and closing it a few times in a row causes it not to work anymore.. open close open -- stops here most of the time I've seen this kind of thing when the server is the same computer. (In that case, the connection is established, but the Revolution app doesn't know and can't use it.) I can't be sure of other cases. Could the server have put you on a black list? Are you sure you are closing? Maybe you have hit the max number of connections for that server. if you wait a little between the first close and the second open, it will sometimes re-connect.. For what I have seen with the same-computer problem, just dragging the window, resizing it, or even minimizing and opening it will fix it. But not waiting. Could we be looking at the same problem? anyone else notice this, or am i the only one hammering? ;-) I was wondering the same. I've been doing some tests on basic TCP sockets. [this feature was noticed in my code as well as the 'simple server/client' available for download on the runrev website] I'll look at that. Or do you have a better stack for demonstrating what you have seen? I have some stacks and some pointers to some tools, should you be interested. running - windows 2000 sp2 That is where I have seen problems. It is not consistent machine to machine. another user has seen the same problem on macos9 ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: sockets - opening and closing
I've seen this kind of thing when the server is the same computer. i'm on the server machine (server and client same machine) and another client in australia (can't physically get further away from me then that ;-) -- Could the server have put you on a black list? i don't have any such feature... yet =) -- Are you sure you are closing? Maybe you have hit the max number of closing yes, there's only myself and matt on the server, plus there's no internally coded limit to the number of users available to connect -- For what I have seen with the same-computer problem, just dragging maybe i'll just throw in a dummy handler before calling the open socket..? -- I'll look at that. Or do you have a better stack for demonstrating we had both used tuviah's excellent client/server while we were developing our own (which hasn't been released) and now we use our client/server.. -- That is where I have seen problems. It is not consistent machine to machine. is anything? ;-) ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: sockets - opening and closing
On Friday, May 3, 2002, at 08:33 PM, Shao Sean wrote: I've seen this kind of thing when the server is the same computer. i'm on the server machine (server and client same machine) and another client in australia (can't physically get further away from me then that ;-) I noticed that a Revolution TCP client on W2K will time out in 21 seconds. Even Australia to Canada should connect in less than that, I think. In my situation, the connection is actually established. You might try checking with repeated netstat -p TCP. Or use TCPmon to watch connections come and go. Or, if your server is relatively quiet, look at traffic with Ethereal or a similar tool. -- Could the server have put you on a black list? i don't have any such feature... yet =) A stab in the dark. -- Are you sure you are closing? Maybe you have hit the max number of closing yes, there's only myself and matt on the server, plus there's no internally coded limit to the number of users available to connect I had to say that; we are on the use-revolution list. -- For what I have seen with the same-computer problem, just dragging maybe i'll just throw in a dummy handler before calling the open socket..? I tried doing all the same things by script and it did not work. (Assuming we are seeing the same thing.) The behavior on W2K is not the same as on OS X, the only other platform I checked. On OS X, an open will get a socket open callback upon establishment, a socketClosed upon refusal, or a socketClosed in 75 seconds otherwise. On Windows 2000, an open will get a socket open callback upon establishment (except for your and my situations ;-), a socket open callback if refused (delayed .9 seconds), and an open callback in 21 seconds if nobody is home. Dar Scott ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
