James Arthur
James Arthur
An initial generated sketch of a Swift client, based on the writing your own client guide. To be verified / improved and potentially extended to support CoreData sync. @paulharter it's...
We have two headers in the HTTP API response: - `electric-chunk-last-offset` - `electric-next-cursor` Both provide values that are meant to be used by a client in the next HTTP request....
Wrap up the DO and example Worker code into some library helpers. Create some specific Cloudflare integration examples in the monorepo. Ideally also benchmark the CDN -> Worker/DO sync to...
Wrap up the [`redis-sync` example](https://github.com/electric-sql/electric/tree/main/examples/redis-sync) into an `@electric-sql/redis` integration library. This can be a relatively simple shim between a ShapeStream and (various?) Redis structures like a Map.
The patterns from the [Phoenix integration](https://electric-sql.com/docs/integrations/phoenix) are very applicable to other server-side / full-stack frameworks. Particularly integrating Electric via URL and serving a route that then returns authorised config to...
https://deploy-preview-2584--electric-next.netlify.app/docs/walkthroughs/
If you add `experimental_live_sse=true` to your live requests, then the server streams SSEs rather than returning immediately when there's new data. Requests are closed after 60 seconds, in order to...
Our shapes guide is currently (increasingly) full of technical details about where clause evaluation etc. What it doesn’t do is a good job of explaining how to use shapes to...
I just wanted to do a pass on this updated section of https://electric-sql.com/docs/guides/troubleshooting#solution-mdash-run-caddy and am raising an issue for us to discuss before doing. I hopped back into this doc...
I appreciate this may not work with caching but … When developing against a larger initial sync, it’s natural to want to know / display progress. When we do an...