Adds the option to run the versioning logic within a queue job

[jivanrij]

These changes make it possible to handle all versioning logic within a queue job.

I don't know if this will be a proper update because this maybe moves the package a bit away from simple and easy.

I needed it for an application that has a huge load of queue jobs (around 5000 per hour). Most of the time the server load was under 1 (at peak moments 2), but after adding versioning it start hitting 2 (10 on peak moments). I needed to remove the versioning because of this.

Now the versioning logic can be handled after those peak moments.

Feel free to give me some points to improve if you see fit and are interested in merging.

[nonoesp]

Hi @jivanrij, this package is being minimally maintained to keep it working. But we won't add new functionality at the moment. Thanks a lot for the pull request either way!

[iateadonut]

@nonoesp if i wrote tests for this, would you want to merge it?

[nonoesp]

Hey! Can you elaborate a bit more on how this works?

[iateadonut]

I haven't looked into the source code, but I assume that it creates a job and puts the job into queue rather than updating the versioning table on update so that updating the versioning table is removed from the current request and does not have to be completed before termination.

It would require a queue running in the background.