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
-`REALTIME_URL` is `'ws://localhost:4000/socket'` when developing locally and `'wss://<project_ref>.supabase.co/realtime/v1'` when connecting to your Supabase project.
81
81
-`API_KEY` is a JWT whose claims must contain `exp` and `role` (existing database role).
82
82
- Channel name can be any `string`.
83
+
- Setting `private` to `true` means that the client will use RLS to determine if the user can connect or not to a given channel.
- Setting `ack` to `true` means that the `channel.send` promise will resolve once server replies with acknowledgement that it received the broadcast message request.
110
+
- Setting `ack` to `true` means that the `channel.send` promise will resolve once server replies with acknowledgment that it received the broadcast message request.
110
111
- Setting `self` to `true` means that the client will receive the broadcast message it sent out.
111
-
- Setting `private` to `true` means that the client will use RLS to determine if the user can connect or not to a given channel.
112
+
113
+
### Broadcast Replay
114
+
115
+
Broadcast Replay enables **private** channels to access messages that were sent earlier. Only messages published via [Broadcast From the Database](https://supabase.com/docs/guides/realtime/broadcast#trigger-broadcast-messages-from-your-database) are available for replay.
116
+
117
+
You can configure replay with the following options:
118
+
119
+
-**`since`** (Required): The epoch timestamp in milliseconds, specifying the earliest point from which messages should be retrieved.
120
+
-**`limit`** (Optional): The number of messages to return. This must be a positive integer, with a maximum value of 25.
0 commit comments