Chip, > On Sep 20, 2018, at 9:24 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I was going to use the pasteboard to pass information to and from the > IP set tracking process, but as I discovered yesterday - this could be > a problem...
The pasteboard commands don't work in preemptive mode, so not really an option if you want the component to work for preemptive processes. > Where Setutl does not care if the set passed ($Setname) is local, > process, or IP. In Setutl's code a check is done on the set name, > looking for the left right arrow pairing (<>), and branches as needed > to manage either 'normal' sets, or IP sets. This, if I understand > correctly, means that the code to manage the IP sets needs to be thread > safe for the Setutl functions (above) to be thread safe; and this > extends to most of Setutl's functionality. I think you are confusing IP sets with IP variables. IP sets can be created and used in preemptive processes. > OR I need a way to Set and Get values across > processes which is thread safe. Prior to version 17 with Storage, I'm not aware of any option other than using the database or the file system. John DeSoi, Ph.D. ********************************************************************** 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 **********************************************************************
