#
eventmachine
Here are 20 public repositories matching this topic...
iodine - HTTP / WebSockets Server for Ruby with Pub/Sub support
ruby
redis
rack
server
webserver
websocket-server
cluster
pubsub
sse
redis-client
websocket-protocol
http-server
eventmachine
event-source
ruby-mri
concurrent-connections
-
Updated
Sep 12, 2020 - C
EventMachine-based RabbitMQ client. Prefer Bunny: http://rubybunny.info. See documentation guides at http://rubyamqp.info.
-
Updated
Mar 27, 2020 - Ruby
em-eventsource is an eventmachine library to consume Server-Sent Events streaming API.
-
Updated
Jul 25, 2020 - Ruby
Another URL shortener based on Event Machine and rack-fiber_pool
-
Updated
Sep 7, 2020 - Ruby
Dockerized skeleton for prooph software Event Machine
-
Updated
Nov 27, 2018 - PHP
Ruby EventMachine Web Socket Redis Pub/Sub Chat Room
-
Updated
Feb 7, 2018 - Ruby
Simple Sinatra shell with all the goodies.
-
Updated
Dec 18, 2018 - Ruby
-
Updated
May 25, 2020 - Ruby
Develop your own tunnel protocol made easy!
-
Updated
Jul 21, 2017 - Ruby
Bomberman implementation for UA Web Challenge backend
-
Updated
Jun 15, 2020 - Ruby
Ruby Eventmachine on OpenWRT CC 15.0.1 - Wifi Pineapples
-
Updated
Nov 18, 2017 - Makefile
An eventmachine-based implementation of the Redis protocol and Redis Cluster
-
Updated
May 9, 2017 - Ruby
Code examples using EventMachine
-
Updated
Sep 6, 2018 - Ruby
The aim of this project is to learn a bit more about EventMachine.
-
Updated
Dec 4, 2016 - Ruby
A small server for chatting through WebSockets
-
Updated
Apr 20, 2017 - Ruby
One web api to query eps(Earnings per Share) values for multiple companies concurrently with eventmachine
-
Updated
May 15, 2019 - Ruby
Improve this page
Add a description, image, and links to the eventmachine topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the eventmachine topic, visit your repo's landing page and select "manage topics."
When we encounter a failure or the circuit is open and a request is rejected I would rather pass an exception as opposed to a plain string. This can then have additional context attached to it such as any underlying exceptions.