Thread Safe Queue Between DLL and EXE

[jharris66]

Hello,

We wondered if this architecture would work:

An exe would create a thread safe queue.   A dll routine would write to the queue using CmtWriteTSQData.   The exe in turn would have an installed callback for the queue for when there are a certain number of items in the queue.

The exe is linked to DLL.

Thank you,

[rkm44]

Hi jharris66, 

It sounds like that architecture you suggest should work. However I am not sure what you mean when you say the exe is linked to the DLL. Could you clarify what you mean when you say that?

Thank you! 

[jharris66]

I basically meant that the exe implicitly links to DLL using *.lib.

I think the architecture appears to be working after some experiments. My main concern initally was whether the thread-safe queue would reside in memory that could be accessed by both DLL and exe.

Thanks,

[rolfk · Accepted solution]

Unless you talk about ActiveX or .Net DLLs (or LabVIEW created DLLs) where there are possible exceptions, any DLL loaded by an application is loaded into the process space of the loading application. As such it uses the heap of the calling application.

[jharris66]

Thanks.  It is our own custom CVI DLL and not ActiveX or .NET.