in reply to •Re: Multiplexed TCP-Client (from: Networkprogramming with Perl)
in thread Multiplexed TCP-Client (from: Networkprogramming with Perl)

...or he could try to learn something. One does not pick up a book that proposes to teach something without intending to learn it. To that end, this example is comletely justified. "You can't know where you're going if you don't know where you've been" applies here as well. Now, if he was trying to use this as actual code, I'd say use the pre-rolled solution. That's not the impression that I got here.

thor

  • Comment on Re: •Re: Multiplexed TCP-Client (from: Networkprogramming with Perl)

Replies are listed 'Best First'.
Re: Re: •Re: Multiplexed TCP-Client (from: Networkprogramming with Perl)
by strat (Canon) on Jul 27, 2002 at 22:03 UTC
    Hello,

    thank you for pointing me to POE, but I'm afraid this is not solving the problem.

    I am new to network programming under Win32, but have got a little bit more experience under Linux or Solaris, esp. with preforking servers and - more in a cargo-cult-manner than with real understanding - POE.

    Some months ago, I played around a little bit with the Multiplexing Server described at How to Write a Chat Server and it was running fine under windows, too.
    Some months ago, I bought the book "Network Programming with Perl", and as I arrived at multiplexing Clients, I thought about writing a client to it (just for fun), threw in the code under Win2k and wondered why it didn't work. I ran it under Linux - no problems. Then I read some documentation again (IO::Select, IO::Socket), and wondered much more.

    This question is not really important for me, but I am very curious how this problem can be solved.

    Best regards,
    perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"