Draft
Conversation
mathiasgrimm
commented
Feb 26, 2026
| $eventId = (string) Str::ulid(); | ||
| $socket = Arr::pull($payload, 'socket'); | ||
|
|
||
| $this->cache->put($this->eventKey($eventId), [ |
Contributor
Author
There was a problem hiding this comment.
The approach here uses a single array for event IDs while storing payloads individually, which I expected to be more efficient.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
wip
Today, polling (Livewire/Inertia) and WebSockets take you down completely different paths — we (I) want to merge them into one.
Polling becomes the default entry point: zero installation, easy local setup, and already production-ready. When you need more performance, swap in WebSockets without changing your code.
This matters especially as less technical users join the ecosystem. Even experienced developers might struggle getting Reverb running locally. Polling removes that friction while keeping you on the same API you'll use in production.
One API (the existing broadcasting one), one path forward.
I don't know if WE really want any of this. But thought we could want that :)
Quick Demo
Frontend (Echo): laravel/echo#479