All geek questions in one place

WCF 4.0, bidirectional

... which options now exist with .NET 4.0, in a way that supports NAT for the client side (i.e., client behind NAT).

I would prefer to use something based on HTTP, but this is a weak condition - I think in the middle of the term I will have some connection without http outside WCF anyway, so a proxy bypass is something I can put off.

Pre.NET 4.0 there was a problem that basically the server> client channel will be open from the server, which made NAT something disjoint.

The survey is unacceptable - we are talking about time sensitivity here.

So what are my options now?

0
source share
2 answers

. NAT , NAT: 34823 192.168.xxx.xxx:80. Microsoft , , . - , Skype ​​, API.

+1

.net 4.0, Windows Azure.

: ( BitTorrent), Relay . / NAT-ed . , , , VoIP, .

Relay , -, . , . , . .

, Microsoft.NET , , . ; . Service Bus : , , .

http://vasters.com/clemensv/PermaLink,guid,92d78bee-2cfd-4a29-95ab-c5abb9b905e7.aspx

0

Source: https://habr.com/ru/post/1741918/

More articles:


All Articles