You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-8Lines changed: 16 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,22 @@ Authors: Andrea Vaccaro - David Grollier
7
7
8
8
A library implementing a high-level actor-based WebSocket communication. An actor can subscribe to a WebSocket Actor (either server or client) to facilitate WebSocket-based communication.
9
9
10
-
Please note that within this library **resource names** as defined in
11
-
the WebSocket protocol specification are referred to as **services.**
10
+
## Main Features
11
+
12
+
* Fully Actor Framework Based
13
+
* Full WebSocket Compatibility
14
+
* Support for WebSocket resources
15
+
* Keepalive infrastructure
16
+
* Secure connection capabilities
17
+
18
+
## Example Code
19
+
20
+
Look in the example folder for a comprehensive set of code examples covering the full functionality of the library.
21
+
22
+
## Note About Nomenclature
23
+
24
+
Please note that within this library **resource names**, as defined in
25
+
the WebSocket protocol specification, are referred to as **services**.
12
26
13
27
# Library
14
28
@@ -89,21 +103,15 @@ This abstract message is sent by either the WebSocket Client or by the
89
103
WebSocket Service to the subscriber Actor on four events:
90
104
91
105
- Connect
92
-
93
106
- Disconnect
94
-
95
107
- Message
96
-
97
108
- Drop
98
109
99
110
For each subscriber Actor a concrete subclass of the message should be created by overriding the methods:
100
111
101
112
- "On Connect.vi"
102
-
103
113
- "On Disconnect.vi"
104
-
105
114
- "On Message.vi"
106
-
107
115
- "On Drop.vi"
108
116
109
117
The subscriber actor can program the required action for the
0 commit comments