I have an important technical query about COM....

I have a small project which requires some work to finish it off.

The scenario is as follows:

I have a VB6 application on server A (it has to be a VB6 app because it has to respond to a DDE request) which needs to launch an application on server B.

The application on server B is also a VB6 application and uses COM to communicate with a third application on server B. The third application on Server B has a GUI which is required to be displayed to the user on server A. so far I have embedded a MSRDPCLIENT object in the application on server A, which successfully launches the application on server B.

The problem comes when a new request is received by server A. The embedded MSRDPCLIENT object only seems to have a disconnect function which doesn’t end the session on sever B – meaning that a new connection request creates a new session – this eats up server resources and will bring server B to a halt very quickly. What I need is a way of communicating to the already established session, telling it of a revised parameter and allowing the existing session to do it’s stuff.

My research has led me to believe that there is something called VirtualChannels which would allow this communication to take place, though I am unsure if this is the case or not.

Hope you can help.

Thanks,

Darren

Darren Brook
email: [email protected]

Well, of course you could pass a "Commit suicide" instruction to the process on B.
Or, you could just keep your communication with the original instance (which apparently is the persistent instance), and just change the subject, so to speak. In otherwords, don't disconnect.

I don't really know anything about the actual question youasked regarding VirtualChannels.