Re:Bridge is a new RPC framework for building modular services
by m0th87 on Tuesday June 26, 2012 @07:31PM
(#4164719)
Few more points:
* Bridge currently uses a central broker, ZeroRPC is broker-less.
* ZeroRPC gives you streaming responses (similar to python generators). Bridge instead provides pub/sub.
* Bridge uses callbacks everywhere, whereas it varies for ZeroRPC based on language implementation. Our node.js version obviously uses callbacks, but the python version doesn't, thanks to gevent.
Re:Bridge is a new RPC framework for building modular services
by vitus on Tuesday June 26, 2012 @07:44PM
(#4164762)
I can't imagine that WebSockets would be used outside of communicating with the browser -- in fact, a quick glance at the Python client library seems to indicate the use of raw TCP sockets.
Re:Bridge is a new RPC framework for building modular services
by m0th87 on Tuesday June 26, 2012 @08:21PM
(#4164889)
Apologies, must've misread something. Removed that point.
Re:Bridge is a new RPC framework for building modular services
by shykes on Tuesday June 26, 2012 @07:23PM
(#4164699)
Actually come to think of it, this is more similar to dotCloudJS by the dotCloud labs team: http://js.dotcloud.com
* ZeroRPC has been open-sourced by dotCloud with no plans for monetization. It's just a fundamental piece of infrastructure which we think is worth sharing. Licensing fundamental infrastructure software is not our business (also: it's very hard).
* I see very interesting scenarios where ZeroRPC can be integrated with Bridge. There is already work on integrating it with systems very similar to Bridge, for example Stack.io (http://github.com/dotcloud/stack.io).