Using function hostAddress immediately after "open socket" (TCP) causes the Revolution application to lock up. Presumably the open is not complete at this point. Using the function hostAddress after the port is open works OK. The problem occurs whether the attempt is failing or not.
This does not apply to "open datagram socket". Presumably it opens immediately. The returned value for hostAddress in this case is 0.0.0.0. I think this is a bug. Foremost, use of the function should not cause a crash. Given that, use of the function should do something reasonable. Presumably, an open attempt will eventually stop for some reason. The behavior in question applies to that interval between the open command and the stop. Maybe something reasonable is one of these: 1. It returns an undefined value. 2. It returns an error string. 3. It returns the valid IP address. I like this one best. 4. It returns the string indication that the argument is not a valid socket. This is OK, too. 5. It returns any of some documented subset of the above. I like the subset corresponding to 3 & 4, best. 5. Maybe there is some reasonable way the function can wait. I don't like this one. This was tested on OS X using 1.1.1 B1. Dar Scott _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
