The way to pass extra options to the underlying ssh process from Net::OpenSSH is using the constructor master_opts argument.

The way to share the SSH connection is to pass around the path to the multiplexing socket (you can retrieve it calling method get_ctl_path).

You can also specify where you want to create the multiplexing socket explicitly (instead of letting the module pick a place for you) with the constructor argument ctl_path. Net::OpenSSH, by default, enforces some security policies for that path that you should obey.

So, for every connection you want to keep open (in your case, four connections every one using a different account), you need a process that establishes the connection and runs the dummy command from time to time. For instance: 

use Net::OpenSSH;

my $account_id = 1;
my $ctl_path = "/.../some/known/place/to/put/the/control/path-$account
+_id";

while (1) {
  eval {
    unlink $ctl_path;
    my $ssh = Net::OpenSSH->new($host, ..., ctl_path => $ctl_path);
    $ssh->die_on_error("Unable to connect to remote host");

    while (1) {
      # run the dummy command
      $ssh->sftp->stat("/") or die "SFTP command failed";
      sleep 10;
    }
  };
  warn $@ if $@;
  warn "delaying before restarting SSH connection\n";
  sleep 5;
}

[download]
Then from the process where you want to do the SFTP operation: 
...

my $ssh = Net::OpenSSH->new(external_master => 1, ctl_path => $ctl_pat
+h);
my $sftp = $ssh->sftp // $ssh->die_on_error("Unable to create SFTP ses
+sion");

# at this point $sftp is a regular Net::SFTP::Foreign object you can u
+se in any way you like.
...

[download]

Most servers limit the number of channels open simultaneously in a single SSH session. For instance, it is 10 by default for OpenSSH. If you expect very many request coming in parallel, that could be a source of problems.

Finally note that allowing direct connections between a web server and other services has some security implications. If the front end becomes compromised, intruders would be able to access those backend services and the data there freely. Because of that, sometimes using an intermediate layer as the queue mechanism proposed in my OP could still be the most sensible thing to do.

Update: Both Net::OpenSSH and Net::SFTP::Foreign allow you to set timeouts for connecting and/or running commands. You should adjust those, to ensure that if any connection becomes stalled, it is discarded and established again, so that services recover promptly.

In reply to Re^5: REST API with SFTP Pooling by salva
in thread REST API with SFTP Pooling by Sukhster

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.