I guess maybe what is needed perhaps for Poser cloud rendering, over limited bandwidth, using queue manager is a little software render helper agent to sit on your rendering machine, along with a web server (Apache or IIS) running a web service.

A python script in Poser, on your workstation could upload the render job as a temporary .pz3 with an additional XML file, containing the render settings, uploading it over http protocol, to the web service, that would accept those files, and then place them in a monitored directory... or at least in some way, handing them over to the render helper agent, which would in turn talk to Queue Manager.... instead of Poser, directly... if you catch my drift.

That latter bit, talking to Queue Manager, is where it probably gets trickier I suppose... and there's perhaps asynchronous event handling needed in there too I guess, more than likely... to keep the originating instance of Poser updated as to progress.

This render agent idea is maybe getting a bit convoluted... if it wasn't nonsense to begin with.

Of course if either Queue Manager or indeed FFRender itself had a python api, that could cut out at least one of those hypothetical software middle men... I don't know, maybe they do???

:-o

Is it telling that when you said 20 years ago, I initially thought 1982... before realising that was now 30 years ago!

Actually, I'm not that old... it's just that I seem to have misplaced 10 years somewhere ;-)