I too would like to see how many calls are in the queue and have voted on the existing requests on the forum.
At the summit I gave a presentation on using a worker process that to provide a means for subscribed client forms to monitor when data in a table is modified. It uses a tables trigger to call the worker when a record is added, modified, or deleted which then executes on subscribed clients a CALL FORM to each subscribed window. During the session Chuck Miller asked a legitimate question as to what happens if a table is modified in bulk for example with an ARRAY TO SELECTION. This would result in thousands of unnecessary Execute on client calls, and I have no idea how the queue might back up. The obvious answer is to disable the trigger before doing any bulk modifications, but I think being able to get the size of the queen would be helpful. A command like GET WORKER QUE would really be helpful if it returned one or more arrays containing information about the call like what process and/or user made the calls. John > On Apr 20, 2018, at 6:04 AM, Tony Pollard via 4D_Tech <[email protected]> > wrote: > > I’d really like to be be able to see the size of a worker queue (as David > Adams and others have said in the past). In my case I want a one-shot (+1 if > the worker is running), which doesn’t look doable if the calling process is > also preemptive - unless I lob everything into the queue with a timestamp. > > Why do I want this? I want to start a sync process which takes 10 seconds or > so to run (an ideal candidate to run preemptively), which may be called from > a trigger or another preemptive process. There may be many thousands of > simultaneous calls, so I want one call if the worker is not running > (semaphore is good enough) and one call to add just one to the queue if it is > running (to mop up data that has changed since the worker executed). > > Having a potentially huge queue seems a waste, but I’m struggling for other > ideas? Sadly I missed the Summits. > > Tony Pollard > Another Dimension > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
