D
dbeavon
Guest
@ Brian : Yes, in the other thread I had mentioned that I was able to eventually use NO-WAIT to make things a bit faster. But I'd really like to find a way to do synchronization in-process, and without making use of a remote database. Using a remote OE database for synchronization of code seems like a very "round-about" approach to solving this problem. And I really don't want to add more than a few milliseconds of overhead since we use the CLR bridge in our "connect-proc" triggers, and any delays that are introduced there will have a substantial negative impact on clients that are making several round-trips to PASOE at once. Matt, I could probably use .Net synchronization once I have an initialized CLR bridge to use. But the synchronization errors I'm facing are happening during the Progress ABL operation which initializes the CLR bridge in the first place. It's a catch-22 of sorts. I was hoping that the ABL language itself has something I can use for synchronization. I should note that I have already tried to "preload" the CLR but that doesn't fix the errors - if anything it makes them worse. I have a case open with tech support but I thought perhaps there may be other ABL programmers who might have found an approach for serializing code that runs within PASOE MS-Agents.
Continue reading...
Continue reading...