So, here it is:
I have a 3'rd party API written in C that is Single Threaded(state is saved
between different commands, locks and so on - so i'v heared).
The only way i was able to use it is with thread sync:
calss A{
public void b()
{
lock(A){....}
}
But as you realize this kills all performance. The next solution would be to
create multiple processes that load the DLL and communicate between the IIS
and this processes. So far i'v tried remoting with both server and client
activated objects but not with much luck. The only thing that worked was
Process.Start("..") but the process dies after performing a task(ofcourse)
and there is no way to send back information from the created porcess.
The general ideea would be to create multiple processes that can execute the
commands that come from IIS(through MSMQueue or something similar). What it
would be great is to have a bare socket from the IIS to each of the "worker"
processes for sending and reciving data.
What i would like to know is:
If there is a simpler way of doing this whole thing?(already tried
COM+/Enterprise Services and a C++ wrapper that unloads the DLL but didn't
work well)
If not, is there a way to create a communication channel between 2 processes
that doesn't include remoting?(bare sockets or someting - i just want to send
string from one place to another :))
PS: API will not change for the next years... :(
PS2:I know it's stange...
Thank you!
