Cannon,
> On Dec 15, 2017, at 10:18 AM, Cannon Smith via 4D_Tech <[email protected]> > wrote: > > Thanks, Arnaud. I was hoping to find someone that could say “Hey, we do that > now and it isn’t a problem” to give me some confidence going forward. But > you’re right, there are other possibilities if it doesn’t work. The 4D HTTP commands are non-blocking. I claim this because I use them for a 4D to 4D remote procedure call implementation. Sometimes I test with both the client side and server side in the same application instance. This is slower, but it works and you can trace method calls on both sides of the interface. There is no way this would work if the client blocked execution until the end of the response. John DeSoi, Ph.D. ********************************************************************** 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] **********************************************************************
