This whole thread-safe concept of preemptive processes only applies to v16+
Why are you worried about making your v13 component thread safe, in v13?
It's not like you can set the "can be run in preemptive processes" method 
property in v13, the source needs to be updated to v16+ just to gain access to 
that method property...

Moving forward, if you want to achieve thread-safety while still providing the 
same level of process interaction that you currently have with IP vars, then I 
would suggest looking at Shared Storage. However, the concept of Shared Storage 
is a feature of v17 and obviously won't work in v13.
http://doc.4d.com/4Dv16R6/4D/16-R6/Storage.301-3649498.en.html

-Tim



**********************************************************************
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
**********************************************************************

Reply via email to