Im looking to do some testing is is possible to use net.tcp bindings in 2022.2 with the smart client.
Pretty sure its fully deprecated at this point. It didn’t work well even in 2021.
1 Like
Long story, but we use net.tcp in 2021 and couldn’t use Windows SSO in 2022.
I did finally discover last week, though, that Azure SSO worked fine for us. (Or basic auth.)
Not sure why you are trying net.tcp but maybe that helps?
here is more information on this. I was going to try using net.tcp on our WAN users computers which was a better performance than smart client over https. i have tested it with version of the smart client and it take 2 to 3 times longer versus 10.2.700 but i can test that now as we have upgraded to 2022.2 in January. I know it is a lot faster with web browser over the WAN. I am talking like 50-60 ms over the tunnel and like over 100 ms from server to users computer that is across the WAN.
Yes, net.tcp is faster. It was not as resilient over WAN connections for us. Any accumulated speed reductions were wiped out by lost connections and reconnect time. This was especially true for laptops as they moved from one access point to another or from work to home. Sometimes the Smart Client would hang so hard, you had to kill it in the Task Agent. This all went away with HTTPS connections.
Are we saying the embedded EO Browser is faster over net.tcp in the Smart Client than a web browser running https without the Smart Client?
That should skip net.tcp.
1 Like
Exactly. Browser, embedded or not, always use https
2 Likes