OT: WS Address Behind Firewall

  • Thread starter Thread starter rawCoder
  • Start date Start date
R

rawCoder

ODD TOPIC

Hi,

Pardon me for this post, sent here for larger active users. Will try to keep
the question simple.


What WS-Address (mechanism) is used to specify a client that needs a WS
Server to send data to the client ( via "Reply To" or whatever method ) BUT
the client is behind a firewall ? ( referring Communication from Web Service
Server to Web Service Client[Consumer] )


Sorry if miniaturization of question increases complexity.

Thank you,
rawCoder
 
WS's protocol SOAP is on HTTP. HTTP is on TCP by PORT 80 so that if client
machine behind firewall can access internet web, it also can access internet
WS. In other words, firewall shouldn't close Tcp Port 80.
 
I'm not talking about the Client accessing the WebService Server.
Its the other way around.
The Server needs to access the Client.

So the problem is that the firewall will block the server access to the
client.
Thats what firewall is about.
Also the IP Address of the client wont be exposed as well.

Hope I made myself a littel clearer.

rawCoder


Rulin Hong said:
WS's protocol SOAP is on HTTP. HTTP is on TCP by PORT 80 so that if client
machine behind firewall can access internet web, it also can access internet
WS. In other words, firewall shouldn't close Tcp Port 80.

rawCoder said:
ODD TOPIC

Hi,

Pardon me for this post, sent here for larger active users. Will try to keep
the question simple.


What WS-Address (mechanism) is used to specify a client that needs a WS
Server to send data to the client ( via "Reply To" or whatever method ) BUT
the client is behind a firewall ? ( referring Communication from Web Service
Server to Web Service Client[Consumer] )


Sorry if miniaturization of question increases complexity.

Thank you,
rawCoder
Click to expand...
Click to expand...
 
The model is always client request/Server reponse.
You must be kidding if you mean server request/ client response.

rawCoder said:
I'm not talking about the Client accessing the WebService Server.
Its the other way around.
The Server needs to access the Client.

So the problem is that the firewall will block the server access to the
client.
Thats what firewall is about.
Also the IP Address of the client wont be exposed as well.

Hope I made myself a littel clearer.

rawCoder


Rulin Hong said:
WS's protocol SOAP is on HTTP. HTTP is on TCP by PORT 80 so that if client
machine behind firewall can access internet web, it also can access internet
WS. In other words, firewall shouldn't close Tcp Port 80.

rawCoder said:
ODD TOPIC

Hi,

Pardon me for this post, sent here for larger active users. Will try to keep
the question simple.


What WS-Address (mechanism) is used to specify a client that needs a WS
Server to send data to the client ( via "Reply To" or whatever method ) BUT
the client is behind a firewall ? ( referring Communication from Web Service
Server to Web Service Client[Consumer] )


Sorry if miniaturization of question increases complexity.

Thank you,
rawCoder
Click to expand...
Click to expand...
Click to expand...
 
By the way. If you want WS-server access your client which is behind
firewall. Simple, just let firewall allow it.
 
I am talking about Publish Subscribe Model.

rawCoder


Rulin Hong said:
The model is always client request/Server reponse.
You must be kidding if you mean server request/ client response.

rawCoder said:
I'm not talking about the Client accessing the WebService Server.
Its the other way around.
The Server needs to access the Client.

So the problem is that the firewall will block the server access to the
client.
Thats what firewall is about.
Also the IP Address of the client wont be exposed as well.

Hope I made myself a littel clearer.

rawCoder


Rulin Hong said:
WS's protocol SOAP is on HTTP. HTTP is on TCP by PORT 80 so that if client
machine behind firewall can access internet web, it also can access internet
WS. In other words, firewall shouldn't close Tcp Port 80.

:

ODD TOPIC

Hi,

Pardon me for this post, sent here for larger active users. Will try
Click to expand...
to
keep
the question simple.


What WS-Address (mechanism) is used to specify a client that needs a WS
Server to send data to the client ( via "Reply To" or whatever
Click to expand...
method )
BUT
the client is behind a firewall ? ( referring Communication from Web Service
Server to Web Service Client[Consumer] )


Sorry if miniaturization of question increases complexity.

Thank you,
rawCoder
Click to expand...
Click to expand...
Click to expand...
 
Whats the use of Web Services (port 80 based ) if I need to get ports
openend in the firewall.
I would rather use Sockets.

rawCoder
 
rawCoder said:
What WS-Address (mechanism) is used to specify a client that needs a WS
Server to send data to the client ( via "Reply To" or whatever method ) BUT
the client is behind a firewall ? ( referring Communication from Web Service
Server to Web Service Client[Consumer] )
Click to expand...

ASP.NET Web Services don't support bidirectional communication
at present. You may try .NET Remoting with a bidirectional channel
(not supplied by MSFT).

bye
Rob
 
rawCoder said:
Whats the use of Web Services (port 80 based ) if I need to get ports
openend in the firewall.
I would rather use Sockets.
Click to expand...

Yep you would. If you looking to register for event channel communications as in the Publisher /
Subscriber model then web services are the worng tool for the job. You would use a web service to
register your client with a central server and then to query that server for information but not to
notify the client that a Publisher event has occured unless of course the client was also a server.

Sounds like your building a peer to peer application. Webservices in this sense are great as a
registration tool but not as the basis for peer/event communications. You could poll the webservice
from the client but polling is always god awful and wouldn't scale very well at all.

Check out this url

http://msdn.microsoft.com/msdnmag/issues/01/02/netpeers/

hth
Richard
 
This Url may even contridict everything i said above.

http://xml.coverpages.org/ni2004-03-05-b.html

I haven;t time to scan through but it looks they have some insight on the subject, but i would be
surprised if they are not talking webservice to webservice i.e client/server hybrid / rather than
(what i assume your talking about) server to desktop event driven notification via webservice?

Richard
 
Back
Top