[pypy-svn] r40208 - pypy/dist/pypy/doc
fijal at codespeak.net
fijal at codespeak.net
Sun Mar 11 14:20:15 CET 2007
Author: fijal
Date: Sun Mar 11 14:20:14 2007
New Revision: 40208
Modified:
pypy/dist/pypy/doc/distribution.txt
Log:
Write a chapter about Pyro
Modified: pypy/dist/pypy/doc/distribution.txt
==============================================================================
--- pypy/dist/pypy/doc/distribution.txt (original)
+++ pypy/dist/pypy/doc/distribution.txt Sun Mar 11 14:20:14 2007
@@ -61,4 +61,29 @@
XXX finish, basic interface, example, build some stuff on top of greenlets
+Related work comparison
+-----------------------
+
+There are a lot of attempts to incorporate RPC mechanism into
+Python, some of them are listed below:
+
+* `Pyro`_ - Pyro stands for PYthon Remote Objects, it's a mechanism of
+ implementing remotely accessible objects in pure python (without modifying
+ interpreter). This is only a remote method call implementation, with
+ all limitations, so:
+
+ - No attribute access
+
+ - Arguments of calls must be picklable on one side and unpicklable on
+ remote side, which means they must share source code, they do not
+ become remote references
+
+ - Exported objects must inherit from specific class and follow certain
+ standards, like \_\_init\_\_ shape.
+
+ - Remote tracebacks only as strings
+
+ - Remote calls usually invokes new threads
+
+.. _`Pyro`: http://pyro.sourceforge.net/
.. _`transparent proxies`: objspace-proxies.html#tproxy
More information about the Pypy-commit
mailing list