Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>YMMV, but here are my results from evaluating RPyC, Pyro4 and ZeroRPC for use on an upcoming project. Note that there are not in-depth tests, nor is this intended to be an in-depth review, just my notes on how well each works for the needs of my upcoming project.</p> <p>ZeroRPC:</p> <ul> <li>quite a few dependencies</li> <li>very young project (main support from dotCloud)</li> <li>very little documentation</li> <li>can't access remote object's attributes, just methods</li> <li>Due to lack of attribute access, IPython tab completion does not work on remote objects</li> </ul> <p>Pyro4:</p> <ul> <li>Python3 support</li> <li>Nice, plentiful documenation</li> <li>mature project</li> <li>No attribute access/IPython tab completion</li> </ul> <p>Pyro3:</p> <ul> <li>support for attribute access (claimed in docs; have not verified)</li> <li>No Python3 support</li> </ul> <p>RPyC:</p> <ul> <li>attribute access, IPython tab completion on remote objects</li> <li>Python3 support (claimed in docs; not yet verified)</li> <li>spotty documentation</li> </ul> <p>FWIW:</p> <p>I tend to like RPyC (maybe because it was my first? ;-), but it's documentation is sparse. It was my first exposure to an RPC, and it took me a long time to "grok" how to get things working. The author (Tomer) is very helpful and does respond to Qs on the Google RPyC list.</p> <p>If you're new to RPC, I would suggest starting with Pyro and take advantage of its solid documentation to learn the ropes. Move on to RPyC, ZeroRPC, etc. as your needs require.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload