>Thanks, but this is a no-installation component on the client side but the actual EXE we already have. This EXE is updating by itself when needed. So, if we add support for this listening, it will be smart enough to return back to expected result to the server. So, basically, instead of client to server, we need server to client. Whatever it takes locally as far as configuration, we can do. If it requires to open a port with a high level of encryption for the transmission, this is doable.
>
>Basically, I need to open a channel between the two. The market software does that, aren't they? I wouldn't think they would hit a WS for every second when they need to update their graph. They need more power so I assume they have a direct channel with a server.

OK, so you're talking about adding listener/server capabilities to your existing .Net .EXE running on the client. If you can open ports, firewalls etc. I'm sure you can get it to work.

You'll have to decide how robust and secure you want it to be, and how it will interact with the rest of your app.

I'm pretty sure the AIO WS utility software just opens up a listener/server on the client. No network traffic happens until someone walks up to the AIO and initiates a scan with the WS as the desired destination. Once the scan completes, a connection to the WS is established and the file is sent.