Bingo, look at the IHttpHandler interface for the server side. You'll need to create your own signaling stream if you want to reach clients behind a firewall. You'll consume this stream on the client side via the HttpWebRequest class. Also be aware that some firewalls close the socket after so many seconds if there isn't any activity. So you'll problaby want to send out a "heartbeat" message every few seconds to all the clients. Most stock ticker programs (ie Datek streamer, etc.) do this.
----- Original Message ----- From: "GiriKrishna Tirumala" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, February 04, 2003 9:42 AM Subject: [ADVANCED-DOTNET] http channel in .NET Remoting > Hello, > I have a specific requirement on using Remoting through a firewall . Let me explain the scenario in brief. > I have a remote object hosted in IIS behind a firewall configured to block all ports other than 8080. I have a client registering an Http channel and specifying > port 0 to receive event callbacks from the remote object. The callbacks are obtained from the server when there is no firewall involved, but with firewall, the callbacks are not obtained. > Iam aware that callbacks are sent from the server on a secondary connection using a random port which is blocked by the firewall and hence these callbacks are not received. > What is the solution to this problem. Should a custom http channel be written.............. > > > Rgds > > Giri > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
