How are the inner workings of BackgroundProcess different from using a non-blocking CURL HTTP request?

Hi,

We are looking into using cron jobs for long running tasks. I am looking into ultimate cron and it's dependency BackgroundProcess. I have been diving a bit into the code of the BackgroundProcess module and it seems like that running a cron job is just done by sending a new GET or POST request.

We are worried that cronjobs will timeout because of the request timeout setting in Apache. Does anyone know if backgroundprocess takes care of this? Cause if not, how is backgroundprocess different from using a non-blocking CURL http request. Apart from of course keeping track of the requests(jobs) in a table with handlers and such.

Long story short; is backgroundprocess affected by any (request) timeout settings set in Apache?

Thank you very much,

Roderick