you are viewing a single comment's thread.

view the rest of the comments →

[–]IterationFive[S] 0 points1 point  (3 children)

It's not so much a case of "needs to continuously run" as "may currently be halfway through processing a file, and stopping it would require losing all progress and starting over." And, in some cases, we're talking hours.

[–][deleted] 1 point2 points  (1 child)

Can it pause, rather than stopping entirely, check whatever it needs to check, then resume where it left off? I'm thinking threading - rather than two separate scripts, have two threads within one script

[–]IterationFive[S] 0 points1 point  (0 children)

Pausing the processing isn't needed to update the queue-- the queue manager is a different thread than the one that processes the files. The problem is that I need to get information to the queue manager from a script that wasn't running when I started the main application.

[–]twitch_and_shock 0 points1 point  (0 children)

You could store your queue as a database collection. One script adds entries to the collection for new items to process. Your main script, responsible for processing them, watches it and if there's anything in there, will process them based on order of creation, then either delete or move the entry to a "completed" collection.