I'm a bit confused. When I just call SAVE RECORD in data entry form (cooperative process), I was told it's not OK because it's from a process that have UI. Now, your latest reply claimed it's OK. Or only if there's no trigger and transaction?
If I create a new process that contain "no" UI from application process, this is again, not OK. When 4D announced preemptive thread is supported in triggers as long as no IP variables, I thought this is game changer that 4D could move to enterprise solution. Obviously, it's just my illusion. It seems all these game changer features in 16 and 17 are only beneficial for 4D based web server but not traditional client/server solution developers. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >DB4D requests (19814) are all preemptive since v11, >so if you call the command SAVE RECORD on the client side (a cooperative >process), >the request is still processed on the server side in preemptive mode (i.e. you >don't congest the server). > >it sort of becomes a moot point that you are calling the command in >cooperative mode, >because the bulk of the work (marshalling data and exchanging it via the >network) is done in preemptive mode any way. same for Begin SQL/End SQL, which >is not thread safe, but of course SQL requests (19812) are all preemptive >since v11. ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
