We are currently working on an API for an existing system.

It basically wraps some web-requests as an easy-to-use library that 3rd party companies should be able to use with our product.

As part of the API, there is an event mechanism where the server can call back to the client via a constantly-running socket connection.

To minimize load on the server, we want to only have one connection per computer. Currently there is a socket open per process, and that could eventually cause load problems if you had multiple applications using the API.

So my question is: if we want to deploy our API as a single standalone assembly, what is the best way to fix our problem?

A couple options we thought of:

• Write an out of process COM object (don't know if that works in .Net)
• Include a second exe file that would be required for events, it would have to single-instance itself, and open a named pipe or something to communicate through multiple processes
• Extract this exe file from an embedded resource and execute it

None of those really seem ideal.

Any better ideas?