in reply to Trying to get started with IO::Multiplex

When I looked at the port numbers I thought it was odd that one was 23 and the other was 2300

You answered your own question. They must be the same.

Sockets are bidirectional, but if the programs setup additional sockets, it should be invisible to you, the end user. See Simple bi-directional forking commandline client. What is usually done, is a forked or threaded client is used, one fork for reading the socket, the other for writing.

Why are you using IO::Multiplex? IO::Select is not hard. See Problem with IO::Select for example.

Also see perl socket examples for a basic intro to how it all works without IO::Multiplex. Look at IO Multiplexing server

Those examples explain the details, but it is often easier to use modules like IO::Select and IO::Socket instead of the raw Perl functions, and you can google for many code snippets previously posted.

Good luck.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh
  • Comment on Re: Trying to get started with IO::Multiplex

Replies are listed 'Best First'.
Re^2: Trying to get started with IO::Multiplex
by Bruce32903 (Scribe) on Jan 16, 2011 at 16:05 UTC
    Thank you for your reply.

    I was typing my follow-up while you added your reply. I was not ignoring your reply.

    My main reason for using IO::Multiplex was that someone told me that it was a much easier way to go. For my first attempt easy sounded good. Except for the four client error messages I now have my first attempt under my belt. Thus, it is a good time (after a little mandatory yard work) to review your comments, review what I have done, review the postings I have used and try to gain a little wisdom as a person with one small program under my belt.

    Having something that works makes it easier for me to go through Perl documentation/examples and learn more about Perl and WireShark one issue at a time. Previously, having nothing working made it hard to zero in on anything.

    Thanks for your suggestions.

    Still looking for suggestions/comments on the error messages.

    Bruce
[reply]

In Section Seekers of Perl Wisdom