support for .Net Remoting

UnSkiLd · Post by **UnSkiLd** » 2005-05-05 14:16

Need a way to change the connection type, and more exports to individual components.

This is incase someone wants to use 'some' of UVNC but not the whole program.

scovel · Post by **scovel** » 2005-05-06 13:05

Why would anyone in their right mind use .NET remoting for anything? Have you tried it? UGLY!

Read this: http://www.thinktecture.com/Resources/R ... Cases.html

Sean

Guest · Post by **Guest** » 2005-05-06 18:22

scovel wrote:Why would anyone in their right mind use .NET remoting for anything? Have you tried it? UGLY!

Read this: http://www.thinktecture.com/Resources/R ... Cases.html

Sean

I beg to differ. I have used it for tons of areas where firewalls are an issue.

For instance at work here we have our clients from all around the united states and they have corporate firewalls along with network nazi's you can still get through their network unless they turn off port 80 all together.

Speed? We send our datasets through .Net Remoting and we compress, encrypt and send huge amounts or data in less than a second.

Another example is the tech support application that I am developing. What are you to do when all the ports are blocked except outbound only on http, which is almost normal for a corporate firewall. Network admins are reluctant to open a port unless they feel comfortable with the application its hitting. Then you deal with NAT's as well.

Well thanks to .Net Remoting you dont have to deal with ports nor firwalls and I am still able to send and recieve images, mouse and keyboard events and chat with the same effeciency as if I was using a direct connection via tcp/ip.

.Net remoting is an all around method if its done right. And in a purely windows environment.

scovel · Post by **scovel** » 2005-05-06 19:23

Guest,

I guess I stand corrected...

Interesting. You have a production application going out over the Internet using .NET remoting?

I'd love to see the code.

IS it reliable?

I've been banging my head against .NET remoting on-and-off. Are you using call-backs (events) or a connection in each direction?

That article (from the "Remoting Guy") turned me completely off to it.

Real-world experience is far more valuable than some guy's paper.

Sean

UnSkiLd · Post by **UnSkiLd** » 2005-05-06 21:05

scovel wrote:Guest,

I guess I stand corrected...

Interesting. You have a production application going out over the Internet using .NET remoting?

I'd love to see the code.

IS it reliable?

I've been banging my head against .NET remoting on-and-off. Are you using call-backs (events) or a connection in each direction?

That article (from the "Remoting Guy") turned me completely off to it.

Real-world experience is far more valuable than some guy's paper.

Sean

Sorry I forgot to put my username last time, guest was me.

Yes it is reliable as long as port 80 is somewhat accessible.

We have had a few scenarios where the network admins were using packet sniffing instead of port sniffing and since our .Net Remoting doesnt use exactly webpage like responses and requests it was being blocked. After explaining to them what .Net Remoting was, figured they should of known, they stopped sniffing our packets (gross!) and filtered us out.

As for sample code. Almost everything I used to complete it can be found at websites like Code Project, www.codeproject.com, and code guru, www.codeguru.com

I recommend it for anyone in a .Net environment that might have to deal with no open ports and a firewall.

Of course you still have Web Services you can use as well, and just like .Net Remoting, there is a time and place to implement it.

HOpe this helps.

UnSkiLd