1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
Source: wslay
Standards-Version: 4.7.2
Maintainer: Anton Gladky <gladk@debian.org>
Section: libs
Priority: optional
Build-Depends:
cmake,
debhelper-compat (= 13),
libcunit1-dev,
nettle-dev,
Build-Depends-Indep:
python3-sphinx,
sphinx-common,
Vcs-Browser: https://salsa.debian.org/debian/wslay
Vcs-Git: https://salsa.debian.org/debian/wslay.git
Homepage: https://github.com/tatsuhiro-t/wslay
Package: libwslay-dev
Architecture: any
Multi-Arch: same
Section: libdevel
Depends:
libwslay1 (= ${binary:Version}),
${misc:Depends},
Description: 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.
Package: libwslay1
Architecture: any
Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends},
Pre-Depends:
${misc:Pre-Depends},
Description: 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.
Package: libwslay-doc
Architecture: all
Multi-Arch: foreign
Section: doc
Depends:
${misc:Depends},
${shlibs:Depends},
${sphinxdoc:Depends},
Description: 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.
|
