zoukankan      html  css  js  c++  java
  • WebSocket TCP HTTP

    RFC 6455 - The WebSocket Protocol https://tools.ietf.org/html/rfc6455

    1.5. Design Philosophy

    
    
       _This section is non-normative._
    
       The WebSocket Protocol is designed on the principle that there should
       be minimal framing (the only framing that exists is to make the
       protocol frame-based instead of stream-based and to support a
       distinction between Unicode text and binary frames).  It is expected
       that metadata would be layered on top of WebSocket by the application
    
    
    
    
    Fette & Melnikov             Standards Track                    [Page 9]

    
    RFC 6455                 The WebSocket Protocol            December 2011
    
    
       layer, in the same way that metadata is layered on top of TCP by the
       application layer (e.g., HTTP).
    
       Conceptually, WebSocket is really just a layer on top of TCP that
       does the following:
    
       o  adds a web origin-based security model for browsers
    
       o  adds an addressing and protocol naming mechanism to support
          multiple services on one port and multiple host names on one IP
          address
    
       o  layers a framing mechanism on top of TCP to get back to the IP
          packet mechanism that TCP is built on, but without length limits
    
       o  includes an additional closing handshake in-band that is designed
          to work in the presence of proxies and other intermediaries
    
       Other than that, WebSocket adds nothing.  Basically it is intended to
       be as close to just exposing raw TCP to script as possible given the
       constraints of the Web.  It's also designed in such a way that its
       servers can share a port with HTTP servers, by having its handshake
       be a valid HTTP Upgrade request.  One could conceptually use other
       protocols to establish client-server messaging, but the intent of
       WebSockets is to provide a relatively simple protocol that can
       coexist with HTTP and deployed HTTP infrastructure (such as proxies)
       and that is as close to TCP as is safe for use with such
       infrastructure given security considerations, with targeted additions
       to simplify usage and keep simple things simple (such as the addition
       of message semantics).
    
       The protocol is intended to be extensible; future versions will
       likely introduce additional concepts such as multiplexing.

    https://github.com/HJava/myBlog

    【译】WebSocket协议第一章——介绍(Introduction) - 掘金 https://juejin.im/post/5b1a7189e51d45068b496cf0

  • 相关阅读:
    牛客网剑指offer第46题——孩子们的游戏(圆圈中最后剩下的数)
    不借助临时变量两数交换篇
    牛客网剑指offer第48题——不用加减乘除做加法
    牛客网剑指offer第44题——翻转单词顺序列
    双指针索引技术
    二叉树的下一个结点
    数组中的逆序对
    丑数
    野指针与空指针
    【转】以操作系统的角度述说线程与进程
  • 原文地址:https://www.cnblogs.com/rsapaper/p/12930009.html
Copyright © 2011-2022 走看看