3 ms·
I started working on this small library some time ago and use it in many of my personal projects. It’s not meant to replace any existing libraries (though you c
by BinaryIdiot 12y ago
I started working on this small library some time ago and use it in many of my personal projects. It’s not meant to replace any existing libraries (though you could certainly use it to replace some things here and there) but to augment by using messaging. I use this quite frequently when I work with web components where I try to make my messages as generic as possible so I can separate my UI from my business logic completely.
Not sure if others will find it useful but figured I’d see what feedback hacker news would have, if any :)
- pcthrowaway 12y agoHi, thanks for sharing. I'm fairly inexperienced with using any kind of message-based event management so my question may reveal a deficit in understanding on my part: Would something like this be a javascript-runtime environment translation of message brokering libraries like ZeroMQ and RabbitMQ? If so, does that mean an application that already utilizes a messaging library such as those two could plug in msngr.js on the client or server-side (if using node) and use messages received from the message broker more directly, instead of having to translate them into emitted events?
- BinaryIdiot 12y agoSo msngr.js currently only works within your current process (so a web page or a node app) and is meant to help organize code and interface with internally, and externally, developed components. I do hope to eventually interface it with other brokering libraries but since it's a small, pet project of mine that's a bit far off I think.