Here's a alpha/beta release of a bidirectional tcp channel... http://www.dotnetremoting.cc/DisplayPage.aspx?key=OSR_BiDirTcpChannel
"This channel aims to solve several problems related to events, callbacks and client-side sponsors when Remoting is used with clients behind NATs or Firewalls."
He also has Jabber & SMTP channels...hmmm interesting.
Hope this helps, Brian
From: Miguel de Icaza <[EMAIL PROTECTED]>
To: Lluis Sanchez <[EMAIL PROTECTED]>
CC: Steve Mentzer <[EMAIL PROTECTED]>,[EMAIL PROTECTED]
Subject: Re: [Mono-list] Bi-directional remoting
Date: 22 Feb 2003 14:37:45 -0500
Hello,
> Certainly, if you want a server to make a call to an object in a client that
> is behind a firewall, you cannot use TcpChannel. It is not designed for
> that.
>
> However, this is a limitation of the TcpChannel, not a limitation of
> Remoting. It is possible to implement a remoting channel that allows
> bi-directional communication between a firewalled client and a server. For
> example, a SMTP/POP3 based channel ;-). The remoting infrastructure is
> indeed very flexible.
You could also create an ssh-tunnel if you are behind a firewall to establish a private connection to the target system (which at the time you have performed a uni-directional call, means that you most likely can establish also an ssh-tunnel).
It would be also possible to create a bidirectional tcp-based channel that does the same: provides a tunnel where bi-directional traffic can live.
This is relatively simple, and should be a good exercise for those of you pondering doing a fun project.
Miguel. _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail
_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
