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
It's also possible to send distinct messages in batches to limit the overhead
124
+
of HTTP headers. There is a current limit of 10 events per batch on
125
+
our multi-tenant clusters.
126
+
127
+
|Argument |Description |
128
+
|:-:|:-:|
129
+
|batch `Array` of `Dict`|**Required** <br> A list of events to trigger |
130
+
131
+
Events are a `Dict` with keys:
132
+
|Argument |Description |
133
+
|:-:|:-:|
134
+
|channel `String`|**Required** <br> The name of the channel to publish to. |
135
+
|name `String`|**Required** <br> The name of the event you wish to trigger. |
136
+
|data `JSONable data`|**Required** <br> The event's payload |
137
+
|socket_id `String`|**Default:`None`** <br> The socket_id of the connection you wish to exclude from receiving the event. You can read more [here](http://pusher.com/docs/duplicates). |
Version 1.0.0 of the library introduced support for event buffering. The purpose of this functionality is to ensure that events that are triggered during whilst a client is offline for a short period of time will still be delivered upon reconnection.
0 commit comments