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
send-buffered-server-evs>ajax-clients! has logic to allow time for possible reconnects during broadcast.
send-buffered-server-evs>ws-clients! does not.
I.e. Ajax broadcasts have a reliability mechanism that WS broadcasts do not.
While it's less critical for WS connections, this might be a nice feature to extend to WS broadcasts too.
The text was updated successfully, but these errors were encountered:
BEFORE THIS COMMIT
- `send-buffered-server-evs>ajax-clients!` has logic to allow time for possible reconnects during broadcast.
- `send-buffered-server-evs>ws-clients!` does not.
I.e. Ajax broadcasts have a reliability mechanism that WS broadcasts do not.
AFTER THIS COMMIT
The same reliability mechanism is now applied to both Ajax and WS broadcasts.
The feature is far less critical for WS broadcasts, but still nice to have.
BEFORE THIS COMMIT
- `send-buffered-server-evs>ajax-clients!` has logic to allow time for possible reconnects during broadcast.
- `send-buffered-server-evs>ws-clients!` does not.
I.e. Ajax broadcasts have a reliability mechanism that WS broadcasts do not.
AFTER THIS COMMIT
The same reliability mechanism is now applied to both Ajax and WS broadcasts.
The feature is far less critical for WS broadcasts, but still nice to have.
Currently:
send-buffered-server-evs>ajax-clients!
has logic to allow time for possible reconnects during broadcast.send-buffered-server-evs>ws-clients!
does not.I.e. Ajax broadcasts have a reliability mechanism that WS broadcasts do not.
While it's less critical for WS connections, this might be a nice feature to extend to WS broadcasts too.
The text was updated successfully, but these errors were encountered: