.net - Any benefits in using TCP for desktop, when server already using WebSockets for web -


we're developing system consists of server written in .net , web client. connected via websockets.

in future, i'd add desktop client system. there point use tcp connection between desktop client , server, when have websocket implementation web , can use desktop too?

not really.

  • websockets connections starts http request, go through firewalls easier socket connnection.
  • websockets starts http behave regular tcp connection.
  • also, of times same tcp port http used websockets, since despite of being different protocol, negotiation starts http.
  • the websocket protocol defines way framing data little overhead.
  • websockets supports transport security tls
  • websockets supports gzip message compression, although not browsers do.
  • but, if want implement own super compression algorithm use desktop clients, can. configure websocket extension, standard browsers never ask extension.

i don't see point of enabling raw tcp connection if have websocket support.


Comments

Popular posts from this blog

java - Oracle EBS .ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class ERROR -

c# - how to use buttonedit in devexpress gridcontrol -

nvd3.js - angularjs-nvd3-directives setting color in legend as well as in chart elements -