zotonic_mod_teleview
braid-spec
zotonic_mod_teleview | braid-spec | |
---|---|---|
2 | 7 | |
4 | 216 | |
- | 0.5% | |
4.0 | 8.1 | |
4 months ago | 5 months ago | |
Erlang | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zotonic_mod_teleview
-
Zotonic, the Erlang Web Framework
Yes indeed. We also have something not more similar to what liveview offers. It is here: https://github.com/mmzeeman/zotonic_mod_teleview. It is based on mqtt, and the views are updated with normal html like templates. This makes it possible for frontenders with html and css knowledge to contribute to a project with a rich SPA like interface.
-
Mark Nottingham: Server-Sent Events, WebSockets, and HTTP
Very interesting. I've implemented something similar. It evolved out of the co-browsing solution I developed for the company I work for.
The solution uses mqtt. Clients subscribe to a topic on the server, and the server publishes patches to update the view. Patches can be incremental (patch against the last frame), cumulative (patch agains the last keyframe) or a new keyframe. It allows for server side rendered views. Multiple clients can subscribe to the same view and keep in sync. See: https://github.com/mmzeeman/zotonic_mod_teleview
braid-spec
-
Synit – A Reactive Operating System
Hi! I have a few questions:
1) What are the benefits of the reactive operating systems? Do you have any example use-cases that this does better than traditional approaches?
2) Do you find this related to functional reactive programming at all?
3) Since this is a model of concurrency with eventual consistency, do you see it benefitting from eventually-consistent OT or CRDT data types?
I am working on what might be a related model: https://braid.org and https://stateb.us. We are building a "distributed state abstraction", that we envision will end up in three places:
a) HTTP will upgrade from a state transfer to a state synchronization protocol
b) Applications will be separated into UIs on top of a "web of state" (see https://stateb.us/static/statebus-demo-3-31.mp4 ) and transition from web apps to app webs
c) Operating Systems will replace file systems with state systems; where local variables in memory can persist to disk without explicit read/write calls, and can be read/written across processes without programming overhead.
I am wondering if we are all looking at the same programming abstraction, but from different angles!
-
Supabase Edge Runtime: Self-Hosted Deno Functions
Thanks Lakshan!
I don't think my use-case is necessarily a good fit for edge functions. I am trying to achieve what Supabase realtime/multiplayer accomplishes, but generically. I participate informally with the https://braid.org IETF working group, which to over-simplify is CRDTs over HTTP with subscriptions.
I'm interested in web standards and that's what's drawn me to deno, so I'm super excited the more and more I see it being adopted. BroadcastChannel piques my interest because it is perfectly in that gray area of standardization-- it makes total sense on the client and we're on the cusp of discovering what that could look like for servers.
In deno deploy, all the instances of my service are able to be linked together by BroadcastChannel, which I'm viewing as a p2p-style architecture. Ultimately, I'm curious about how this works under the hood and if it would be possible to interoperate a BroadcastChannel between Deno Deploy, Supabase, and say a Raspberry Pi in my house.
I've gone on a bit of a tangent, but I think maybe I should get involved with the WinterCG, since now that I'm putting my thoughts to words-- seems like it fits their charter.
-
Jack Dorsey: a native internet protocol for social media
Yes! This is the approach we're taking at https://braid.org -- extending HTTP itself into a decentralized synchronization protocol, so that any application built on top of it can be decentralized.
Specifically, you can divide any application's protocol into two parts:
- A data synchronization protocol
-
What Is JSON Patch?
That doesn't work, because DELETE is defined to delete the entire resource. PUT is defined to replace the resource with the body, which would replace the resource with the patch. Only PATCH is defined to accept a patch and do something special with it.
Another option, though, is to use the Range-Patch spec from: https://github.com/braid-org/braid-spec
- Braid: Synchronization for HTTP
-
Mark Nottingham: Server-Sent Events, WebSockets, and HTTP
Your use-case sounds perfect for Braid: https://braid.org
This works like SSE, but is designed specifically to articulate changes to the state of HTTP/REST resources.
If you're in Javascript, you can use the braidify library: https://www.npmjs.com/package/braidify
What are some alternatives?
canonic - QML web browser
eventhub - A high performance pub/sub over WebSocket server written in modern C++.
pushpin - A proxy server for adding push to your API, used at the core of Fastly's Fanout service
know-your-ietf-well - IETF Internet-Drafts, RFCs, erratas, ABNFs
zotonic_mod_doom_fire
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
styx - Simple, high-performance event streaming broker
http-core - Core HTTP Specifications
zotonic - Zotonic - The Erlang Web Framework & CMS