I have a stored procedure that watches a table in the database. This Store procedure then executes call rocker depending on the tasks placed in the table. Depending on what is put into the record of the table it will cell multiple workers. Each worker could run for un undetermined amount of time. But usually they are pretty quick.
The problem is that is I put in multiple requests. The call worker seems to lose track of the process running. For instance I have a worker called upload photo. This worker takes a photo from the table and places it in a folder on the server and generates three different sized thumbnails. But I have found that my loop pushing photos to the server moves so fast it outraces the call worker and causes requested workers to fail to finish processing. I have found the docs discussion about using signals. But I am wondering if there is a best practice for using this in the loop to prevent my from doing a call worker to a busy worker but not stall the event looks on the server. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
