Programming in Practice
Information ComputationExternal Data Management Adaptive ProgrammingConcurrent ProgrammingDistributed Programming
  • Programming in Practice
    • References
  • Information Computation
    • Repository Description
    • Course Description
    • Fundamentals
      • Introduction
      • Information versus data
      • Algorithm Versus Program
    • Information Representation
      • Coding System versus Type
      • Custom Types
      • Object-oriented programming
      • Anonymous Types
      • Partial Definitions
      • Generic Types and Methods
    • Algorithm Implementation
      • Program Layered Architecture
      • Inter Layer Communication
      • Dependency Injection
    • Summary
      • Conclusion
  • External Data Management
    • Executive Summary
    • Data Streams
      • Preface
      • Implementation Examples
      • Objects Serialization
      • Cryptography
    • Functional Programming
      • Delegate and Events
      • Extension Methods
      • Anonymous Functions
    • Structural Data
      • LINQ Expression
      • LINQ to Object
      • LINQ to SQL
    • Graphical Data
      • MVVM Program Design Pattern
      • User Interface Description
  • Adaptive Programming
    • Executive Summary
    • Application Architecture
    • Composition
    • Reflection
    • Configuration
  • Concurrent Programming
    • Executive Summary
  • Distributed Programming
    • Executive Summary
    • Client-Server Communication
      • Rest API
      • WebSocket API
Powered by GitBook
On this page
  • Introduction
  • See also
Edit on GitHub
  1. Distributed Programming
  2. Client-Server Communication

WebSocket API

Last updated 2 years ago

The example has been derived from the project

Introduction

The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).

See also

M. Postol; NBlockchain; NBlockchain/P2PPrototocol/NodeJSAPI/
The WebSocket Protocol; Request for Comments: 6455; 2011
The WebSocket API; W3C Candidate Recommendation 20 September 2012
M. Postol; NBlockchain; NBlockchain/P2PPrototocol/NodeJSAPI/; Rel.1.0