Remoting basics

[Volker Hetzer]

Hi!
We are thinking about using C# for a client-server application.
The scenario is like this:
We've got an old Automation enabled single threaded application.
We hope to do a COM component that can be loaded by the application,
starts a second thread and then serves requests.
The second thread will only communicate with "our" code running
in the Application thread.
The goal is that an external application can connect to the
second thread, which in turn communicates with the first thread.
That way we can call our own methods and retrieve results and events,
which is not possible if we just used the applications COM interface.

What I've seen so far from microsofts overview documents is that
server objects are always created by a server on demand. However, that
is not what we want. We want our component to start up when the application
starts, and the server to redirect requests to that existing component
instead of creating a new instance.

Is this possible?

Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.

[Brandon]

Should be able to have your object contact the server and say "yo, I'm over
here now" when initialized and then the server and grab that request and add
it to the queue of where to send messages.
--
KMG Software, Inc.
Thinking Beyond, Above, and Before
http://www.kmgsoftware.com
"Volker Hetzer" wrote:

Hi!
We are thinking about using C# for a client-server application.
The scenario is like this:
We've got an old Automation enabled single threaded application.
We hope to do a COM component that can be loaded by the application,
starts a second thread and then serves requests.
The second thread will only communicate with "our" code running
in the Application thread.
The goal is that an external application can connect to the
second thread, which in turn communicates with the first thread.
That way we can call our own methods and retrieve results and events,
which is not possible if we just used the applications COM interface.

What I've seen so far from microsofts overview documents is that
server objects are always created by a server on demand. However, that
is not what we want. We want our component to start up when the application
starts, and the server to redirect requests to that existing component
instead of creating a new instance.

Is this possible?

Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.