5 ms·
sthatipamala is correct. A few more points on the differences between ZeroRPC and Bridge: * ZeroRPC has been open-sourced by dotCloud with no plans for monetiz
by shykes 14y ago
sthatipamala is correct. A few more points on the differences between ZeroRPC and Bridge:
* 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 http://github.com/dotcloud/stack.io).
- shykes 14y agoActually come to think of it, this is more similar to dotCloudJS by the dotCloud labs team: http://js.dotcloud.com http://js.dotcloud.com
- m0th87 14y agoFew 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.