IP Driver and with IN-Memory Driver Caching

2

  1. The template support for the in-memory driver has never done me any good. I just hand code everything I need from the In-Memory driver.

  2. Be warned that the in-memory driver, despite what the documentation says, is not THREAD safe. It should NOT be used on the server side for SET/NEXT loops. Most of the time it will probably work client-side, assuming you don’t let the user trigger multiple threads doing SET/NEXT loops on the same memory table. The problem has been reported to SV with an app that always reproduces the problem, but the issue has been given a low priority.

  3. Look for a thread safe QUEUE library from a 3rd party. If I have to write any more code where I want something like the In-Memory Driver (but something that works) then that is the route I will be going.

1 Like