 firebird wire protocolFirebird Wire Protocol Carlos Guzman Alvarez, Mark Rotteveel Version 0.15, 26 December 2021 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.2.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 40 页 | 213.15 KB | 1 年前3 firebird wire protocolFirebird Wire Protocol Carlos Guzman Alvarez, Mark Rotteveel Version 0.15, 26 December 2021 Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.1.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.2.1. Deviations for protocol version 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 码力 | 40 页 | 213.15 KB | 1 年前3
 MySQL wire protocol (Oct 31, 2023)Serge Klochkov (Integrations Team) 31 October 2023 Agenda Motivation and Context 01 MySQL Wire Protocol Compatibility 02 MySQL SQL Dialect Compatibility 03 2 Motivation 3 ClickHouse and Other Databases not like that. MySQL user’s password has to be encrypted with Double SHA1 What does “MySQL Wire Protocol” mean? 6 ● TCP Connection ● MySQL authentication support ● Incoming command packets handler Result set protocols - text and binary * https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_PROTOCOL.html How it started … 7 What is “command \x16”? ? QuickSight Tableau Online How it started0 码力 | 16 页 | 3.04 MB | 1 年前3 MySQL wire protocol (Oct 31, 2023)Serge Klochkov (Integrations Team) 31 October 2023 Agenda Motivation and Context 01 MySQL Wire Protocol Compatibility 02 MySQL SQL Dialect Compatibility 03 2 Motivation 3 ClickHouse and Other Databases not like that. MySQL user’s password has to be encrypted with Double SHA1 What does “MySQL Wire Protocol” mean? 6 ● TCP Connection ● MySQL authentication support ● Incoming command packets handler Result set protocols - text and binary * https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_PROTOCOL.html How it started … 7 What is “command \x16”? ? QuickSight Tableau Online How it started0 码力 | 16 页 | 3.04 MB | 1 年前3
 websockets Documentation
Release 9.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with Transport Layer Security (TLS) {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) localhost_pem = pathlib.Path(__file__).with_name("localhost.pem") ssl_context.load_ certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) localhost_pem = pathlib.Path(__file__).with_name("localhost.pem") ssl_context.load_0 码力 | 81 页 | 352.88 KB | 1 年前3 websockets Documentation
Release 9.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with Transport Layer Security (TLS) {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) localhost_pem = pathlib.Path(__file__).with_name("localhost.pem") ssl_context.load_ certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) localhost_pem = pathlib.Path(__file__).with_name("localhost.pem") ssl_context.load_0 码力 | 81 页 | 352.88 KB | 1 年前3
 websockets Documentation
Release 4.0sheet 2.1.1 Server • Write a coroutine that handles a single connection. It receives a websocket protocol instance and the URI path in argument. – Call recv() and send() to receive and send messages at subclass WebSocketServerProtocol and pass either this sub- class or a factory function as the create_protocol argument. 2.1.2 Client • Create a client with connect() which is similar to asyncio’s create_connection() subclass WebSocketClientProtocol and pass either this sub- class or a factory function as the create_protocol argument. • Call recv() and send() to receive and send messages at any time. • You may ping()0 码力 | 48 页 | 224.70 KB | 1 年前3 websockets Documentation
Release 4.0sheet 2.1.1 Server • Write a coroutine that handles a single connection. It receives a websocket protocol instance and the URI path in argument. – Call recv() and send() to receive and send messages at subclass WebSocketServerProtocol and pass either this sub- class or a factory function as the create_protocol argument. 2.1.2 Client • Create a client with connect() which is similar to asyncio’s create_connection() subclass WebSocketClientProtocol and pass either this sub- class or a factory function as the create_protocol argument. • Call recv() and send() to receive and send messages at any time. • You may ping()0 码力 | 48 页 | 224.70 KB | 1 年前3
 websockets Documentation
Release 5.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with TLS. WSS requires TLS certificates {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) ssl_context.load_cert_chain( pathlib.Path(__file__).with_name('localhost.pem')) start_server certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) ssl_context.load_verify_locations( pathlib.Path(__file__).with_name('localhost.pem'))0 码力 | 56 页 | 245.43 KB | 1 年前3 websockets Documentation
Release 5.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with TLS. WSS requires TLS certificates {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) ssl_context.load_cert_chain( pathlib.Path(__file__).with_name('localhost.pem')) start_server certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) ssl_context.load_verify_locations( pathlib.Path(__file__).with_name('localhost.pem'))0 码力 | 56 页 | 245.43 KB | 1 年前3
 websockets Documentation
Release 6.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with TLS. WSS requires TLS certificates {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) ssl_context.load_cert_chain( pathlib.Path(__file__).with_name('localhost.pem')) start_server certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) ssl_context.load_verify_locations( pathlib.Path(__file__).with_name('localhost.pem'))0 码力 | 58 页 | 253.08 KB | 1 年前3 websockets Documentation
Release 6.0confidentiality and also reliability because they reduce the risk of interference by bad proxies. The WSS protocol is to WS what HTTPS is to HTTP: the connection is encrypted with TLS. WSS requires TLS certificates {name}!" await websocket.send(greeting) print(f"> {greeting}") ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER) ssl_context.load_cert_chain( pathlib.Path(__file__).with_name('localhost.pem')) start_server certificate import asyncio import pathlib import ssl import websockets ssl_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT) ssl_context.load_verify_locations( pathlib.Path(__file__).with_name('localhost.pem'))0 码力 | 58 页 | 253.08 KB | 1 年前3
 websockets Documentation
Release 3.4Cheat sheet Server • Write a coroutine that handles a single connection. It receives a websocket protocol instance and the URI path in argument. – Call recv() and send() to receive and send messages at subclass WebSocketServerProtocol and pass either this sub- class or a factory function as the create_protocol argument. Client • Create a client with connect() which is similar to asyncio’s create_connection() subclass WebSocketClientProtocol and pass either this sub- class or a factory function as the create_protocol argument. • Call recv() and send() to receive and send messages at any time. • You may ping()0 码力 | 36 页 | 192.66 KB | 1 年前3 websockets Documentation
Release 3.4Cheat sheet Server • Write a coroutine that handles a single connection. It receives a websocket protocol instance and the URI path in argument. – Call recv() and send() to receive and send messages at subclass WebSocketServerProtocol and pass either this sub- class or a factory function as the create_protocol argument. Client • Create a client with connect() which is similar to asyncio’s create_connection() subclass WebSocketClientProtocol and pass either this sub- class or a factory function as the create_protocol argument. • Call recv() and send() to receive and send messages at any time. • You may ping()0 码力 | 36 页 | 192.66 KB | 1 年前3
 Spring Framwork Web on Reactive Stack v5.3.36 SNAPSHOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.1.1. The Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . representations (e.g. Netty ByteBuf, java.nio.ByteBuffer, etc.) and is what all codecs work on. See Data Buffers and Codecs in the "Spring Core" section for more on this topic. The spring-core module provides decoder implementations. The spring-web module provides Jackson JSON, Jackson Smile, JAXB2, Protocol Buffers and other encoders and decoders along with web-only HTTP message reader and writer implementations0 码力 | 182 页 | 2.52 MB | 1 年前3 Spring Framwork Web on Reactive Stack v5.3.36 SNAPSHOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 5.1.1. The Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . representations (e.g. Netty ByteBuf, java.nio.ByteBuffer, etc.) and is what all codecs work on. See Data Buffers and Codecs in the "Spring Core" section for more on this topic. The spring-core module provides decoder implementations. The spring-web module provides Jackson JSON, Jackson Smile, JAXB2, Protocol Buffers and other encoders and decoders along with web-only HTTP message reader and writer implementations0 码力 | 182 页 | 2.52 MB | 1 年前3
 Using Modern C++ to Build XOffsetDatastructureor object state into a format that can be stored (e.g. files in secondary storage devices, data buffers in primary storage devices) or transmitted (e.g. data streams over computer networks) and reconstructed or object state into a format that can be stored (e.g. files in secondary storage devices, data buffers in primary storage devices) or transmitted (e.g. data streams over computer networks) and reconstructed XOffsetDatastructure, CppCon 2024 252.2 Current Solutions • The 2 Categories • MessagePack, Protocol Buffers, etc. • FlatBuffers, Cap’n Proto, etc. • Input, Output, and Process. // To better understand0 码力 | 111 页 | 3.03 MB | 6 月前3 Using Modern C++ to Build XOffsetDatastructureor object state into a format that can be stored (e.g. files in secondary storage devices, data buffers in primary storage devices) or transmitted (e.g. data streams over computer networks) and reconstructed or object state into a format that can be stored (e.g. files in secondary storage devices, data buffers in primary storage devices) or transmitted (e.g. data streams over computer networks) and reconstructed XOffsetDatastructure, CppCon 2024 252.2 Current Solutions • The 2 Categories • MessagePack, Protocol Buffers, etc. • FlatBuffers, Cap’n Proto, etc. • Input, Output, and Process. // To better understand0 码力 | 111 页 | 3.03 MB | 6 月前3
 PostgreSQL 17beta1 A4 Documentation.............................................................. 1529 47.3. Streaming Replication Protocol Interface .............................................. 1531 xi PostgreSQL 17beta1 Documentation ..................................................................... 2384 53. Frontend/Backend Protocol ........................................................................... 2385 53.1. Overview Documentation 53.4. Streaming Replication Protocol ........................................................... 2402 53.5. Logical Streaming Replication Protocol ........................................0 码力 | 3017 页 | 14.45 MB | 1 年前3 PostgreSQL 17beta1 A4 Documentation.............................................................. 1529 47.3. Streaming Replication Protocol Interface .............................................. 1531 xi PostgreSQL 17beta1 Documentation ..................................................................... 2384 53. Frontend/Backend Protocol ........................................................................... 2385 53.1. Overview Documentation 53.4. Streaming Replication Protocol ........................................................... 2402 53.5. Logical Streaming Replication Protocol ........................................0 码力 | 3017 页 | 14.45 MB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100














 
  
  
 