POE is indeed shiney good value. But to answer your other questions, you don't need two ports, you can just read and write to the same socket. The data won't get mixed up.

As regards shifting information around, it is traditional to do "callbacks" - calling a subroutine to process data that you read, calling a subroutine to prepare some data, and then sending the prepared data. Things like event queues and packet queues are sometimes useful.

The big reason not to do this is that while you are doing anything, you aren't waiting for the next connection, or the next packet of data. This will probably only show up under load i.e. when you use it for real for the first time.

This is the way it tends to go:

while (1)
{
$new_conn = do_select();
add_connection( $new_conn ) if $new_conn;
read_all_connections();
process_data();
write_all_connections();
}

[download]

but it gets very messy since you have to maintain state information for each socket, etc. Which is why a object interface like POE is a great idea.

____________________
Jeremy
I didn't believe in evil until I dated it.

In reply to Re: Non-forked, bi-directional client/server by jepri
in thread Non-forked, bi-directional client/server by Coruscate

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.