67c7f5c083
13 described in RFC 6455. This library offers 2 levels of API: event-based API and frame-based low-level API. For event-based API, it is suitable for non-blocking reactor pattern style. You can set callbacks in various events. For frame-based API, you can send WebSocket frame directly. Wslay only supports data transfer part of WebSocket protocol and does not perform opening handshake in HTTP. Wslay supports: * Text/Binary messages. * Automatic ping reply. * Callback interface. * External event loop. Wslay does not perform any I/O operations for its own. Instead, it offers callbacks for them. This makes Wslay independent on any I/O frameworks, SSL, sockets, etc. This makes Wslay protable across various platforms and the application authors can choose freely I/O frameworks.
6 lines
395 B
Text
6 lines
395 B
Text
$NetBSD: distinfo,v 1.1 2016/04/23 18:32:09 adam Exp $
|
|
|
|
SHA1 (wslay-1.0.0.tar.gz) = 1c8b4a765787a96dd32512d399ba4a1df06fa0a3
|
|
RMD160 (wslay-1.0.0.tar.gz) = cfbb20bf7520aafa24ae7d874c61e1f5fc905e35
|
|
SHA512 (wslay-1.0.0.tar.gz) = 12aadf5a36a38efcbec68f42bc49f6fdc272be44b986e2ca26d6bf0660bf39437a400a7f33de9d8abfad0b2fde64ffef32cea5a586868aa33fa685e257e39a35
|
|
Size (wslay-1.0.0.tar.gz) = 45846 bytes
|