I don't see why it would not work. I'm not aware of any real difference between a worker and a regular 4D process except that a worker has queue of requests and lives until killed whereas a regular process executes one request and exists.
I tend to use the 4D progress component with some wrappers that allow it to be used by any process or worker including hidden and preemptive. It can also monitor and cancel jobs executing on the server. A lot of work to set up, but usable for almost anything once it is in place. John DeSoi, Ph.D. > On Mar 27, 2020, at 11:29 AM, Jeremy Roussak via 4D_Tech > <[email protected]> wrote: > > Is there any objection to that method of doing things? The documentation > doesn’t suggest that workers can’t have a UI. Maybe I’m stretching the use of > a worker process past that which was intended. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
