Thank you very much for the great replies everybody! >Also, on a pedantic note, you cannot have multiple processes listening >on a single port. Using SO_REUSEADDR means that multiple processes can >bind to the port, but only one at a time can listen.
This addresses my issue nicely. I thought I was going insane, and now I know it just doesn't work that way. Someone suggested not to write servers in Perl on Win32. But it is so compelling to do so! In any case, I don't have the ability at this time to code in the languages mentioned. I *could* pull it off with assembly language, but I don't want to. Fork() seems to work just fine on Win32, except there seems to be a 64 process limit. Even that would be fine if I could get those threads to terminate and give those resources back to the system. Explaining my rational, a single process server would probably work fine most of the time. But sometimes I need to telnet 25 to the server manually for testing, and this would tie up the process for a long time causing other inbound connections to time out. Again, thank you all. This is turning out to be a very interesting list! Barry Brevik _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
