wslay 1.1.1-4~build1 source package in Ubuntu
Changelog
wslay (1.1.1-4~build1) mantic; urgency=medium * Upload to mantic -- Gianfranco Costamagna <email address hidden> Fri, 04 Aug 2023 00:40:30 +0200
Upload details
- Uploaded by:
- Gianfranco Costamagna
- Uploaded to:
- Mantic
- Original maintainer:
- Anton Gladky
- Architectures:
- any all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section |
---|
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
wslay_1.1.1.orig.tar.gz | 50.4 KiB | 7b9f4b9df09adaa6e07ec309b68ab376c0db2cfd916613023b52a47adfda224a |
wslay_1.1.1-4~build1.debian.tar.xz | 7.0 KiB | c040df48a4a5bda8c78b883b4407f1ecb151d53f67b38261d2a1498630016d0c |
wslay_1.1.1-4~build1.dsc | 2.1 KiB | 705830951295a4de9d6397b3663d210e9c9ba040820dc7e12038a4a7058e61a4 |
Available diffs
Binary packages built by this source
- libwslay-dev: WebSocket library written in C. Development files
WebSocket library written in C. It implements the protocol version 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 portable across various
platforms and the application authors can choose freely I/O frameworks.
.
The binary contains development files.
- libwslay-doc: WebSocket library written in C. Documentation
WebSocket library written in C. It implements the protocol version 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 portable across various
platforms and the application authors can choose freely I/O frameworks.
.
The binary contains documentation.
- libwslay1: WebSocket library written in C. Shared library
WebSocket library written in C. It implements the protocol version 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 portable across various
platforms and the application authors can choose freely I/O frameworks.
.
The binary contains shared library.
- libwslay1-dbgsym: debug symbols for libwslay1