By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,851 Members | 1,121 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,851 IT Pros & Developers. It's quick & easy.

Accessing Remote objects in an XML Web Service - Which port is use

P: n/a
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
Nov 23 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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

Nov 23 '05 #2

P: n/a
Hello Dilip and everybody else,

Thank you - that explains why I did not found it in the documentation of
remoting.

One intriguing thing I came across with this architecture concerns
HttpChannel. When accessing the host for the remote object, the Windows
Service (NT Service), I did not need to declare a TcpChannel and register it
in the client, i.e. the XML Web Servic. If a TcpChannel is declared and
registered the application will not work.

The ideas for the server/client architecture using Remoting I got from:
http://www.mastercsharp.com/chapter_06.htm

There it explicitly says that a declaration of the channel and registration
is needed in the client. However, when I modified the client and uncommented
the declaration and registration of the channel it still worked. This was
illogical and I do not have an explanation! Is there any obvious reason I am
missing concerning Remoting?

Regards,
Fredric Ragnar
I got the

"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


Nov 23 '05 #3

P: n/a
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


Nov 23 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.