Remoting in the Internet

[Gomez]

I want to us remoting on the Internet and I saw in a codeproject that its
not recommended because of problems with firewalls and routers.
This seems correct, but I wonder if its really not common in p2p
applications, and if experts in this NG know of any other alternatives to
that...
Regards
Gomez

 

[Arne Vajhøj]

I want to us remoting on the Internet and I saw in a codeproject that its
not recommended because of problems with firewalls and routers.
This seems correct, but I wonder if its really not common in p2p
applications, and if experts in this NG know of any other alternatives to
that...

I don't think P2P apps uses remoting. If a P2P are written in .NET then
my guess is that it will use either plain TCP sockets or UDP or
HTTP. Usually P2P is about moving data not doing RPC style interactions.
P2P app still have firewall problems also though.

Arne

 

[Mirs]

Thanks Mr. Arne,
I guise I was misleading a little as I didn't mention the exact purpose of
the p2p communication. Actually the use is for messaging and also file
transfer. Under these conditions, do you still think that plain sockets or
Http are still preferred? If so why than?
Thanks again
Gomez

 

[Arne Vajhøj]

I guise I was misleading a little as I didn't mention the exact purpose of
the p2p communication. Actually the use is for messaging and also file
transfer. Under these conditions, do you still think that plain sockets or
Http are still preferred? If so why than?

Most likely.

The force of remoting is the automatic marshal and
unmarshal of parameters in the RPC call.

I don't think that will be useful at all in your
type of app.

Arne

 

[John Vottero]

I want to us remoting on the Internet and I saw in a codeproject that its
not recommended because of problems with firewalls and routers.
This seems correct, but I wonder if its really not common in p2p
applications, and if experts in this NG know of any other alternatives to
that...

Remoting works fine across the internet as long as you have a clear
definition of client and server. This precludes the use of events which
essentially reverses the client/server roles. When your remoting client
connects to your server, it has the same problems that any TCP/IP app would
have, the port must be allowed through firewalls etc. If you're working
across the internet, the server cannot establish a connection to the client
because there is probably a NAT router or firewall that would be prevent the
connection. That is true with any TCP/IP app.