Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(zero-cache): handle messages from the mutator websocket connection #3770

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tantaman
Copy link
Contributor

No description provided.

The mutator/pusher will have its own websocket connection. Make the `Connection` class reusable by
parameterizing it with a `messageHandler`
Copy link

vercel bot commented Feb 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
replicache-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 11, 2025 9:45pm
zbugs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 11, 2025 9:45pm

Copy link

🐰 Bencher Report

Branchmlaw/handoff
Testbedlocalhost
Click to view all benchmark results
BenchmarkFile SizeBenchmark Result
kilobytes (KB)
(Result Δ%)
Upper Boundary
kilobytes (KB)
(Limit %)
zero-package.tgz📈 view plot
🚷 view threshold
954.44
(0.00%)Baseline: 954.44
973.53
(98.04%)
zero.js📈 view plot
🚷 view threshold
179.73
(0.00%)Baseline: 179.73
183.32
(98.04%)
zero.js.br📈 view plot
🚷 view threshold
49.99
(0.00%)Baseline: 49.99
50.99
(98.04%)
🐰 View full continuous benchmarking report in Bencher

@tantaman tantaman force-pushed the mlaw/refactor-connection branch from 51e3a29 to f265a1c Compare February 12, 2025 13:58
tantaman added a commit that referenced this pull request Feb 12, 2025
…nection

The end state is to put the pusher/mutator on its own websocket connection (#3770).

This requires some refactoring of the client. Till that is done (and so you all can use custom mutators while I'm on vacation), handle push messages over the existing websocket connection.
tantaman added a commit that referenced this pull request Feb 12, 2025
…nection

The end state is to put the pusher/mutator on its own websocket connection (#3770).

This requires some refactoring of the client. Till that is done (and so you all can use custom mutators while I'm on vacation), handle push messages over the existing websocket connection.
tantaman added a commit that referenced this pull request Feb 12, 2025
…nection

The end state is to put the pusher/mutator on its own websocket connection (#3770).

This requires some refactoring of the client. Till that is done (and so you all can use custom mutators while I'm on vacation), handle push messages over the existing websocket connection.
@tantaman tantaman force-pushed the mlaw/refactor-connection branch 2 times, most recently from a6d7dd7 to 6505299 Compare February 13, 2025 14:41
Base automatically changed from mlaw/refactor-connection to main February 13, 2025 14:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant