comment on

I amend my statement as far as "all 8 messages at once" since most messages only go one way. Like so:

Response message - RECEIVE to SEND task on both sides (ILS and EMS will handle this message - contains code notifying that message was accepted or rejected by socket)
Ping message - SEND to RECEIVE task (this acts as the "keep alive" mechanism) Pings are sent from both sides at 40-second intervals.
Add message - ILS to EMS only
Delete message - ILS to EMS only
Return message - ILS to EMS only
Request message - ILS to EMS only
Status Check message - ILS to EMS only
Status message - EMS to ILS only

As a visual representation, a typical transaction would follow this order:

ILS            EMS
---            ---
Request   -->  
          <--  Response (request accepted/rejected)
          <--  Status (requested item in available/unavailable)
Response  -->
[download]

In reply to Re^3: Multiple Perl files sharing a single socket - is it possible/sensible? by ljamison
in thread Multiple Perl files sharing a single socket - is it possible/sensible? by ljamison

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks