Hello Dilip and everybody else,
Thank you. That was helpful and it explains why I did not find it in the
documentation.
There is one intriguing fact I came across in this prototype using the
HttpChannel class. I based the client/server architecture idea from:
http://www.mastercsharp.com/chapter_06.htm. There it says that the client has
to declare a HttpChannel and register it. When using that concept in my
client, i.e. the XML Web Service, only one call is possible since the service
stops responding after one call to a remote object. Uncommenting the
declaration of the HttpChannel and registration solves the malfunctioning
service.
I went back to the sample client/server solution from
http://www.mastercsharp.com/chapter_06.htm and uncommented the declaration of
the HttpChannel and registration of the channel in the client and it worked
anyway.
This seems illogical. However, I must miss something obvius feature in
Remoting. The question is then why does it work to invoke a method on a
remote object without declaring and register a HttpChannel in the client?
Regards,
Fredric Ragnar
"Dilip Krishnan" wrote:
Hello Fredric,
There is no notion of a port on the outbound request... I believe the
.net implementation for tcp/ip just opens a socket to the remoting host.
HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com
Hi,
I am making a prototype system with Remoting in the bottom of the
system. An XML Web Service is using the remote object on an IIS to
present data.
I am using a TcpChannel for communicating between the XML Web Service
and the host for the remote object. Within the host a port is defined
and the channel registered. It starts listening for requests. The
destination port is therefore clearly defined.
However, when using the remote object in the XML Web Service - what is
the outgoing port for the communication with the listening host?
Architecture:
Client
|
|HTTP Port 80
|
XML Web Service
|
Port? |TCP Port 8080
|
Host for remote object
Thanks,
Fredric Ragnar
