You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have the ability to easily extend the helper class.
In my case, I cannot write to the file system. Instead, I would extend Helper's acquireLock(), releaseLock(), & getLockLifetime() functions to make them read / write to a table.
BackgroundJob accepts a third parameter for the helper class, but run-job does not pass anything for that parameter.
My alternative is to extend Jobby to make the property 'script' a different script that would do the same thing as run-job, but pass BackgroundJob a new Helper class. Is this the route you would recommend?
The text was updated successfully, but these errors were encountered:
@creativebum2 That sounds right to me. You would need to wrap all locking queries in a transaction to ensure you don't get multiple jobs accessing the same lock at once. You could also make it an abstraction to support different databases e.g. mysql, pgsql, etc.
It would be nice to have the ability to easily extend the helper class.
In my case, I cannot write to the file system. Instead, I would extend Helper's acquireLock(), releaseLock(), & getLockLifetime() functions to make them read / write to a table.
BackgroundJob accepts a third parameter for the helper class, but run-job does not pass anything for that parameter.
My alternative is to extend Jobby to make the property 'script' a different script that would do the same thing as run-job, but pass BackgroundJob a new Helper class. Is this the route you would recommend?
The text was updated successfully, but these errors were encountered: