this post was submitted on 26 Aug 2023
80 points (100.0% liked)
Technology
37800 readers
84 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The GitHub, if you're wondering how exactly this thing works. A blog explaining it, and an example.
Is there any particular reason HTTP couldn't have done all this?
HTTPS is heavy when you’re talking about the extreme low power, bandwidth, and compute devices matter is intending to support
its also not a broadcast protocol - matter intends to connect many devices to many devices
those are off the top of my head; i’m sure there are more. HTTP is great, but new/alternate network protocols aren’t inherently bad: especially when you’re operating in a very constrained/niche environment
Yeah, I'm going to reserve judgement, but anything to do with IoT does make me suspicious off the bat.
Does it? It sounded like it was a server-client model in the blog post and a skim of the example, with devices as clients and whatever application as a server.