3 ms·
This looks really interesting, I really like the metadata idea. Readme could do with some more info about delivery guarantees, error handling, the query languag
by geoah 6y ago
This looks really interesting, I really like the metadata idea. Readme could do with some more info about delivery guarantees, error handling, the query language, and overall a bit more information on how the routing works when multiple clients match or no client matches etc.
The protocol doc answers some of these questions I think but generally not the place to go.
I’m not a fan of the mongodb like query language being used as it gives too much freedom to the developer using singyeong, something thay might result in unintended consequences.
I’ll definitely give it a shot, might try hacking a go client together.
Thank you for building and sharing this with everyone!
- notamy 6y agoThanks for the feedback! > This looks really interesting, I really like the metadata idea. I've sorta learned over time that a lot of people tend to hack together a bespoke version of this for a lot of things, so it makes sense to me to make a more generic implementation. > Readme could do with some more info about [...] Erk, yes. I'll add it to my TODO list. > I’m not a fan of the mongodb like query language being used as it gives too much freedom to the developer using singyeong, something thay might result in unintended consequences. A lot of it is genuinely just that I don't really have enough experience in language design to design a better one; I went with what I knew would work reasonably well and wouldn't be painful to generate for end-users. I'm open to ideas for how to improve it if you have any! ^^ > I’ll definitely give it a shot, might try hacking a go client together. I'm really interested in any feedback you might come up with from the actual usage experience.