Re^3: Pre-Forking Daemon with Parallel::ForkManager

Your application sounds like a perfect use case for an application speaking REST (or not) served by one of the modern web application frameworks, e.g. Dancer2 or Mojolicious, which come with preforking servers built in. It's not necessary to build your own frameowrk for that part of your application.

Hope this helps!

The way forward always starts with a minimal test.

Comment on Re^3: Pre-Forking Daemon with Parallel::ForkManager

Replies are listed 'Best First'.
Re^4: Pre-Forking Daemon with Parallel::ForkManager by enemyofthestate (Monk) on Oct 18, 2019 at 16:42 UTC
If only :) For the foreseeable future, the format for the request is a pipe delimited string delivered over a socket connection. I've advocated converting to a GET or JSON format but too many legacy client programs are tied to the pipe-delimited string. That is not likely to change before I retire... One irony is I already wrote a fast-cgi running inside Apache. It takes a GET request, processes it and then returns a JSON formatted response.	[reply]

Replies are listed 'Best First'.

Re^4: Pre-Forking Daemon with Parallel::ForkManager
by enemyofthestate (Monk) on Oct 18, 2019 at 16:42 UTC

If only :)

For the foreseeable future, the format for the request is a pipe delimited string delivered over a socket connection. I've advocated converting to a GET or JSON format but too many legacy client programs are tied to the pipe-delimited string. That is not likely to change before I retire...

One irony is I already wrote a fast-cgi running inside Apache. It takes a GET request, processes it and then returns a JSON formatted response.

[reply]