This PR implements the startup proc in Jester' settings, which then is passed on to httpbeast. The startup proc will run in each httpbeast-thread at initialization.
As is, this PR only implements the startup proc to be used, when jester is running with httpbeast.
The concept for "only allowing" with httpbeast follows the previous numThreads implementation.
Would this be a possible PR? Or are there any changes you would like to see?
Notes:
Hi Dom,
A follow-up PR from the httpbeast PR https://github.com/dom96/httpbeast/pull/89 :)
startup
proc in Jester' settings, which then is passed on to httpbeast. Thestartup
proc will run in each httpbeast-thread at initialization.startup
proc to be used, when jester is running with httpbeast.numThreads
implementation.Would this be a possible PR? Or are there any changes you would like to see?