D
dbeavon
Guest
>> I'm curious to hear what solution you eventually arrive at. My strategy for these types of things is to reach out of ABL into the .Net runtime (via the CLR bridge). The CLR can be used in-process, and all requests to the CLR use a shared appdomain. There are some simple primitives in the CLR that I can use for synchronization. When I first posted the question, the problem was that there was a bug in the CLR bridge itself. The bug was that the CLR bridge initialization would fail - this was caused by concurrent ABL sessions that were all trying to launch at once. So it was a "catch-22" - I couldn't use the CLR bridge to synchronize my ABL sessions (threads) because the CLR bridge wasn't being initialized properly in the first place, due to synchronization problems.
Continue reading...
Continue reading...