Hi,
pls read inline:
In article <#Xz$mSjnDHA.1488@TK2MSFTNGP12.phx.gbl>,
anson.p_o_o_n@torontosquare.com says...
[quoted text, click to view] > Hello,
>
> I would like to clarify something about Remoting Object in .NET.
>
> Knowing from MSDN that in order for Remote Object to work, I need 3
> components.
> a) RemotableType object, just like a regular dll with additional remotable
> feature.
> b) Host Application, which is a listener listens for remote clients of a
> remotable type
> c) Client Application, which is an application that creates an instance of
> your remotable type and accesses designated members.
>
>
> I would like to know:
> (1) Can I run remote object without a web server (IIS)?
Yes, the server part (you call it listener) can be
1. console app - usually for test apps, or while creating
2. windows service
3. hosted in IIS - the advantage is that you can use SSL,
authentications, etc., but you can not use TCP. And it is slower than
windows service.
[quoted text, click to view] > (2) Can I run remote object without having a server program (host
> application or listener) running and
> waiting for a client call?
Hmm, I'm now sure I can understand you. The purpose of remoting is, that
there is a client which makes a calls, and server which executes the
calls. But you can run server and client on the same machine.
If you do not have server(listener) who will receive the calls?
[quoted text, click to view] > if no, can I utilize the proxy feature without using the listener?
The proxy is created when you invoke "new" or Activator.GetObject. At
that moment no call is made to the server. The connection is established
and call is made when client makes a method call on the remote object.
And, you can create a local copy of the same type of object if you
haven't set up the remoting system. I.e. in the shared dll you may have
a class implementation of MyRemoteObject, and if you are offline (you
make the logic how to decide), you can create a local object with new
MyRemoteObject();
[quoted text, click to view] > (3) Can I call (from PC1) a remote object in another PC (e.g. PC2) and then
> the remote object call another remote object in PC3. totally, 3 PC involves?
>
Yes, as many as you want. The sweet thing is, that PC2 can return to PC1
the reference to a remote object on PC3, and the invoking a method on
that object on PC1 will directly be passed to PC3.
[quoted text, click to view] >
> Thank you
>
> Anson
>
>
>
>
>
Hope that helps