The model that I am currently developing involves three elements:
In my mind, the client application (#1) posts a query string to the ASP.NET/IIS web server (#2), which informs the local Windows process (#3) of the query parameters, executes the desired function, and returns the data to #2 then that to #1.
The necessity of such a (seemingly) convoluted procession arises from the nature of the Windows process. This console application uses RPC to connect and authenticate itself against a second server. As you can imagine, this process is expensive.
If I merge the Windows process and ASP.NET/IIS page, then a new connection is opened with every request. This is hardly reasonable if dozens of POSTs are made in quick succession, since each authentication case takes about four seconds.
Fortunately, the Windows console application can login once and maintain the session. Therefore, I must find a solution to interface with this console application, given the the source of any interaction will derive from an ASP.NET/IIS page.
I've read nearly every post on Stackoverflow/MSDN concerning topics encompassing this issue. I know that I can employ remoting, pipes, sockets, WCF, etc.
So I ask all of you: If you've encountered a similar issue, how did you solve it? I'm merely asking for a definitive point in the correct direction. If you can include code, I'll appreciate your response even more.
Thank you very much for any and all help.
