Re^2: Multiple Perl files sharing a single socket

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

It is entirely possible for the server side to be ready for multiple client connections. I would guess EMS has no problem if all eight of your client scripts connect to it at once. Is there some order which needs to be enforced on these messages, or are they fine to arrive in any order?

Comment on Re^2: Multiple Perl files sharing a single socket - is it possible/sensible?

Replies are listed 'Best First'.
Re^3: Multiple Perl files sharing a single socket - is it possible/sensible? by ljamison (Sexton) on Dec 02, 2015 at 15:27 UTC
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]	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Multiple Perl files sharing a single socket - is it possible/sensible?
by ljamison (Sexton) on Dec 02, 2015 at 15:27 UTC

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]

[reply]
[d/l]

In Section Seekers of Perl Wisdom