Ken Kolda
9/10/2004 3:10:00 PM
This can be a big problem over WANs. I highly recommend you look at the
GenuineChannels product (www.genuinechannels.com). This basically uses a
bi-directional connection between the client and server (at least when using
the TcpChannel replacement) so events from the server come across the same
connection. For the HTTP channel, the client actually creates two
connections to the server -- one for client-initiated communication and the
other for server callbacks. This resolves your NAT issues since every
connection comes from the client (it also resolves other WAN-related issues
in .NET remoting).
Ken
"Scott Anderson" <ScottAnderson@donotspam.com> wrote in message
news:5508D2F4-1935-4B6E-BD6F-47F7C9DBB23E@microsoft.com...
> The standard remoting model has the server connect back to the client for
the
> callbacks/events. Is it possible to use the same remoting framework, but
> have the client initiate the callback/event channel? This would solve
many
> firewall and NAT issues related to remoting events without using two-way
> channels or 3rd party channels.