In response to David's statement... Question: "We can't use preemptive threads." Answer: "So what."
I have been in a situation where because 4D could not handle preemptive threading we ended up setting up a RAIC with NGINX in front of it. NGINX load balanced the requests to multiple 4D workstations to handle requests because of some peak load issues where a single thread was literally killing us. The RAIC mostly solved the problem but, managing a bunch of computers vs 1 server that could easily handle the same load in a pre-emptive environment was a hassle. My reason for bringing this lack of non-preemptive support for A4D, NTK etc. was simply to make sure people are considering all aspects of the decisions they are making. With that said I, have probably done 30+ 4D databases on the web and have done it in just about every imaginable way (WS4D, Lightning, 4DWebPack 2.0, 4D For Flex, A4D, NTK, ITK, Contextual, Non-Contextual etc). In only 1 case was the lack of pre-emptive support an issue. Thanks Justin Will ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
