if you take out the "chatter" part, it works perfectly. You can run the program, do "telnet localhost 1000", and it will echo each line you send back at you. That part has been OK for weeks, until I tried to add this reporter function. It's like a file - readline on $SOCK to get a line, writeline to it to reply.
In all honesty, there is another approach I can take that avoides this - just have the client poll the server for the report periodically, I just thought it is neater to say "start reporting" ... "stop reporting" than sending repeated requests. I'll take a look at some other options people have given though. Thanks. On 10/27/06, Chris Wagner <[EMAIL PROTECTED]> wrote: > That code doesn't really make sense. It looks like ur trying to talk to > urself on the same port?? Make a seperate script that listens on a port and > just prints whatever it gets to the screen. Then have ur threaded app do > the talking in a threaded environment. And ur never putting anything in the > message queue. The worker thread needs to "do something" and write messages > into the queue for the socket thread to dequeue and transmit. > > > > > > > -- > REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=-- > "...ne cede malis" > > 00000100 > > _______________________________________________ > Perl-Win32-Users mailing list > Perl-Win32-Users@listserv.ActiveState.com > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > -- Daniel McBrearty email : danielmcbrearty at gmail.com www.engoi.com : the multi - language vocab trainer BTW : 0873928131 _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
