 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / December 2004Bi-directional SOAP messaging possible?
Is it possible to send and receive messages across the same endpoints, using WSE 2.0 ? E.g.: 1. Client (behind firewall) opens a tcp connection to a server on the servers port 80 2. Client sends 0..n messages 3. Server replies asynchronously with 0..n messages For this to work across the firewall, it would require something like this: Client:2805 ----> Server:80 Server:80 ----> Client:2805 It seems to me that there is no way to control the port chosen by the SoapSender - you can only specify the destination endpoint. If this is not possible with SoapSender/SoapReceiver, then it would seem logical that SoapClient/SoapService also would fail across a firewall, since the service would receive a request to its listening port, but would send its reply from another random port. Sounds like what I need is a SoapSenderReceiver class :D Your input is greatly appreciated! -Inge > Is it possible to send and receive messages across the same endpoints, > using WSE 2.0 ? [quoted text clipped - 17 lines] > firewall, since the service would receive a request to its listening > port, but would send its reply from another random port. I don't *think* this is possible with WSE 2.0. First off, it's not really a SOAP issue as much as it is a transport protocol issue. If HTTP is your transport, then it's definitely not possible since HTTP is synchronus request-response. However there is the soap.tcp protocol. I'm relatively certain that soap.tcp is implemented the same way (sync. req-resp). If the server needs to send a message back to the client, it actually reverses the roles and opens a completely differenct connection back to the client. That said, there's nothing preventing you from sending/receiving SOAP messages this way if you felt like inventing your own custom transport protocol. :) HTH, Drew >> Is it possible to send and receive messages across the same endpoints, >> using WSE 2.0 ? [quoted text clipped - 29 lines] > messages this way if you felt like inventing your own custom transport > protocol. :) Thanks for the reply. I am talking about using the soap.tcp, yes. This basically means that there is no way to use Soap Messaging (i.e. SoapSender/SoapReceiver or derived thereof) to communicate from a client behind a firewall, and to a server. Where's the fun in that? (come on, someone prove me wrong - or come up with a preexisting transport protocol allowing me to use WSE/soap messaging bidirectionally through a TCP connection) -Inge > This basically means that there is no way to use Soap Messaging (i.e. > SoapSender/SoapReceiver or derived thereof) to communicate from a > client behind a firewall, and to a server. That's correct. There's no way for a server to communicate back to the client asynchronusly in the case of a firewall. > Where's the fun in that? > > (come on, someone prove me wrong - or come up with a preexisting > transport protocol allowing me to use WSE/soap messaging > bidirectionally through a TCP connection) Hey man, blame the firewalls not the protocols. :) The protocols are perfectly capable of it, it's the fact that all ports on the client are most likely blocked so nobody can build anything around the assumption that they'll be able to communicate back. I agree it sucks, but that's what years of virii and DDoS trojans has brought us to. :\ Later, Drew Hi, I'm working on a custom transport for WSE2 that uses a two-way TCP connection. Basically, the client establishes the connection by sending a message (with a SoapSender as usual), and then later when the service wants to send messages back to the client, the message goes through the same physical connection. I've got the TcpStockSoapReceiver quickstart sample running on top of the transport. I'll probably publish the source somewhere once I'm satisfied with it (I need to make it more robust). In the meantime, send me email to sami at capehill dot net if you want to check out the early version. I'd be glad if someone tried it and gave me some feedback. (We have a long weekend coming so I might not be able to get back to you for the next couple of days...) Regards, Sami > Is it possible to send and receive messages across the same endpoints, > using WSE 2.0 ? [quoted text clipped - 25 lines] > > -Inge Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.