4 ms·
It's such a grief that there is no ruby support yet. It would help a lot with our current project where we have site written in ruby/rails and backend services
by densh 14y ago
It's such a grief that there is no ruby support yet. It would help a lot with our current project where we have site written in ruby/rails and backend services in python. We currently use Redis a broker between the two. At the same we've been looking at zeromq as a possible and simpler alternative.
Can developers share some info about their current roadmap? What languages will be supported next?
- m0th87 14y agoWe did python and node.js first because we use them a lot internally. There's no firm roadmap for future implementations, but we're hoping once the protocol is well-documented, implementations can start growing organically.
- shykes 14y agoNote that a Redis transport is something we're considering. Also check out stack.io: http://github.com/dotcloud/stack.io http://github.com/dotcloud/stack.io
- brunoqc 14y agoWould a redis transport replace zeromq and what would be the advantages?
- shykes 14y agoNo, it would be an additional option. ZeroMQ will always be supported - we use it enormously at dotCloud. Another transport we plan on supporting is websocket. Each transport has its advantages. Zmq is incredibly efficient, very flexible and leaves you in full control of your network topology, but it requires a firewalled trusted network, and doesn't provide ready-to-use broker or naming facilities. Redis can be used as a very efficient broker and discovery component, and can be more easily included in your web stack, but it limits your flexibility and becomes a potential spof. The good news is, once zerorpc supports multiple transports you can stary with one and swap it out for another without changing your code.
- lonestar 14y agoCheck out JSON-RPC. Jimson is a good JSON-RPC client for Ruby. http://github.com/chriskite/jimson http://github.com/chriskite/jimson