confidentiality 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_

sheet 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()

confidentiality 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'))

confidentiality 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'))

Cheat 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()

expected because output buffers were being reused across requests on a long-lived connection and each buffer would not be freed until it was full or the connection was closed. Buffers are now rotated per-request closes a socket unexpectedly there was potential for memory leaks in which data was written to the buffers after they were closed, causing them to reopen. See https://github.com/Pylons/waitress/pull/239 Fix app_iter may never cleanup data that has already been sent. This would cause buffers in waitress to grow without bounds. These buffers now properly rotate and release their data. See https://github.com/Pylo

expected because output buffers were being reused across requests on a long-lived connection and each buffer would not be freed until it was full or the connection was closed. Buffers are now rotated per-request closes a socket unexpectedly there was potential for memory leaks in which data was written to the buffers after they were closed, causing them to reopen. See https://github.com/Pylons/waitress/pull/239 Fix app_iter may never cleanup data that has already been sent. This would cause buffers in waitress to grow without bounds. These buffers now properly rotate and release their data. See https://github.com/Pylo

expected because output buffers were being reused across requests on a long-lived connection and each buffer would not be freed until it was full or the connection was closed. Buffers are now rotated per-request closes a socket unexpectedly there was potential for memory leaks in which data was written to the buffers after they were closed, causing them to reopen. See https://github.com/Pylons/waitress/pull/239 Fix app_iter may never cleanup data that has already been sent. This would cause buffers in waitress to grow without bounds. These buffers now properly rotate and release their data. See https://github.com/Pylo

header. • Dont hang a thread up trying to send data to slow clients. • Supports wsgi.file_wrapper protocol. 10 Chapter 1. Extended Documentation waitress Documentation, Release 2.1.2 1.6 waitress API is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds Linux, /proc/sys/net/ipv4/ tcp_wmem controls the minimum, default, and maximum sizes of TCP write buffers. Default: 1 1.7. Arguments to waitress.serve 13 waitress Documentation, Release 2.1.2 Deprecated

header. • Dont hang a thread up trying to send data to slow clients. • Supports wsgi.file_wrapper protocol. 10 Chapter 1. Extended Documentation waitress Documentation, Release 2.1.1 1.6 waitress API is full, the client may receive an error with an indication of ECONNREFUSED or, if the underlying protocol supports retransmission, the request may be ignored so that a later reattempt at connection succeeds Linux, /proc/sys/net/ipv4/ tcp_wmem controls the minimum, default, and maximum sizes of TCP write buffers. Default: 1 1.7. Arguments to waitress.serve 13 waitress Documentation, Release 2.1.1 Deprecated