On Jan 30, 2019, at 12:07 PM, Timothy Penner via 4D_Tech <[email protected]> wrote: > >> I understand, but I think I am having a problem. >> Suppose our app depends heavily on UI (and it does😊) >> .... > > Simple approach: > > Have the UI spin off the work into a new pre-emptive process (or use workers > ala the CALL WORKER command). > Then have the pre-emptive processes/workers callback to the form using the > CALL FORM command. > This approach allows the pre-emptive processes to push updates back to the > cooperative User Interface. > > Watch the demo from the 2016 summit on the blog: > https://blog.4d.com/4d-summit-2016-laurent-esnault-presents-workers-and-ui-in-preemptive-mode/ > > -Tim
Piotr mentioned that they are using 4D OCI, not the 4D database. I haven’t really kept up with the pre-emptive restrictions, but can plugins specify that they can run pre-emptively? Given some of the other limitations I’d have assumed plugins would be required to run in the cooperative main thread. Jim Crate ********************************************************************** 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] **********************************************************************
