in reply to REST API with SFTP Pooling
Sharing SFTP connections between processes or threads is not a good idea. Too complicated and too difficult to get it right*.
A simplest approach would be to have 5 workers, every one with a dedicated SFTP connection, listen for requests on the same socket/pipe/queue/whatever. When a new request arrives, the first one able to catch it handles it.
On the part of the code where it waits for new requests, a timeout can be set in order to send the dummy command if nothing happens for a while.
*) well, unless the limit is not on SFTP connections but in SSH connections. It is pretty easy to reuse SSH connections with something like Net::OpenSSH, and then run SFTP on top of it.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: REST API with SFTP Pooling
by Fletch (Bishop) on Nov 12, 2020 at 14:27 UTC | |
by salva (Canon) on Nov 13, 2020 at 09:02 UTC | |
Re^2: REST API with SFTP Pooling
by Sukhster (Novice) on Nov 14, 2020 at 05:44 UTC | |
by salva (Canon) on Nov 14, 2020 at 06:38 UTC | |
by Sukhster (Novice) on Nov 16, 2020 at 15:01 UTC | |
by salva (Canon) on Nov 16, 2020 at 16:05 UTC |
In Section
Seekers of Perl Wisdom