@@ -218,7 +218,7 @@ Just import these 3 files to your application and you are ready to go.
218
218
- ** Send Websocket Notify** - dynamic_action_plugin_de_danielh_sendwsnotify.sql
219
219
- ** Show Websocket Notify** - dynamic_action_plugin_de_danielh_showwsnotify.sql
220
220
221
- For a detailed description of the plugins, read further under "Usage Section" or import the demo app sql file to you workspace.
221
+ For a detailed description of the plugins, read further under "Usage Section" or import the demo app sql file to your workspace.
222
222
223
223
224
224
## Usage
@@ -229,15 +229,15 @@ As mentioned in the installation steps, the node notification server component c
229
229
230
230
- ** REST-Interface**
231
231
232
- Sending messages and notifications to users which are connected over the websocket interface.
232
+ Sending messages and notifications to users which are connected to the websocket interface.
233
233
234
234
- ** Websocket-Interface**
235
235
236
236
Connecting and authenticating users against the node server and still more to receive live messages on client browser from server part.
237
237
There exists 2 rooms/namespaces which users can subscribe to:
238
238
239
- - ** private** - For single user messages to all instances of one user (e.g. one user is logged in with 3 browsers)
240
- - ** public** - For single user messages to all instances of one user * AND* broadcasting messages to all connected clients
239
+ - **private** - For single user messages to all instances of one user (e.g. one user is logged in with 3 browsers)
240
+ - **public** - For single user messages to all instances of one user *AND* broadcasting messages to all connected clients
241
241
242
242
- ** Helper pages**
243
243
@@ -251,22 +251,22 @@ General settings of the node server like IP, port, authentication, SSL support a
251
251
252
252
### REST-Service
253
253
254
- The REST-Service is designed to send messages to connected websocket users. Base-URL scheme with looks like this:
254
+ The REST-Service is designed to send messages to connected websocket users. Base-URL scheme looks like this:
255
255
256
256
```
257
257
Type: GET
258
258
http://[host-ip-of-server]:[port]/notifyuser
259
259
```
260
260
261
261
- ** URL-Parameter**
262
- - userid (required) - User-ID of connected user, ** in APEX APP_USER is used* *
263
- - room (required) - Websocket room - valid values: private,public
264
- - type (required) - Notification type - valid values: info,success,warn,error
265
- - optparam (optional) - Optional Parameter string to send any kind of information tp the websocket client
262
+ - ** userid** (required) - User-ID of connected user, * in APEX APP_USER is used*
263
+ - ** room** (required) - Websocket room - * valid values: private,public*
264
+ - ** type** (required) - Notification type - * valid values: info,success,warn,error*
265
+ - ** optparam** (optional) - Optional Parameter string to send any kind of information to the websocket client
266
266
267
267
- ** HTTP Header-Variables**
268
- - notify-title (required) - Title of notification
269
- - notify-message (required) - Message content of notification
268
+ - ** notify-title** (required) - Title of notification
269
+ - ** notify-message** (required) - Message content of notification
270
270
271
271
A demo call using curl could look like this:
272
272
0 commit comments