3 ms·
If you find this interesting, you might also be interested in DripDrop( https://github.com/andrewvc/dripdrop https://github.com/andrewvc/dripdrop ), which is an
by andrewvc 16y ago
If you find this interesting, you might also be interested in DripDrop( https://github.com/andrewvc/dripdrop https://github.com/andrewvc/dripdrop ), which is an alternate approach to the fusion of ZeroMQ, HTTP, and WebSockets.
It's not a general purpose web server, but targets message passing applications that must move between transports. For instance Browser <-> Web Socket <-> ZMQ is easily possible in it.
It's based on ruby eventmachine (no external daemons needed), and lets you seamlessly pass messages between all three protocols, leveraging the differences of each in interesting ways.
Additionally, it's got tools to help you build isolated components that communicate via messaging only (preferably ZMQ). If you keep this in mind from the start, it can substantially help when it comes to scaling out.
Lastly, we're working on Mongrel2 support as a front end.
- LoicProcrast 16y agoI don't know DripDrop (nice name), but messaging is really the way to go. For example with Photon or any system really embracing the message passing approach of Mongrel2, you can get an HTTP request and send back an answer to other connection over jsSocktet (real time analytics for example) or even directly into an HTTP stream (chunked encoding in long polling). The flexibility to easily address a message to a given connection from everywhere at the backend level is what is wonderful in the protocol developed by Zed.