WingNews logo WingNews
top | item 45346431

(no title)

nicr_22 | 5 months ago

Interesting direction, thanks for sharing.

If you're interested in this space it's worth looking at data-star.dev. who takes hypermedia in the opposite direction - one endpoint per page, then push updates to components over SSE.

My worry with MESH is that many endpoints might become a (sorry) mess...

discuss

order

alex-moon|5 months ago

I remember seeing this on the HN front page a while back! I subsequently forgot all about it, of course. Helps to see it again a second time, especially with the new context - I might give it a try next, see how I go. Thanks for the reminder!

andersmurphy|5 months ago

It does require a mind shift as generally you have one connection morphing in all your updates and do CQRS.

The connection per component model that mesh uses is fine until you have concerns that cross across components (this was an issue hotwire also ran into before they introduced morph/refresh).

Instead you have one endpoint per page re-render the whole page via morph on every change. You still have backend components they just send requests up and get their updates via the sse connection for that page. Kinda like view = f (state) just over the network.