News
2009.09.22
RPyC 3.0.7 has been released; fixes some minor bugs
2009.05.31
Marcin Cieslik created rpycd - a UNIX daemon wrapper for classic_server.py
2009.04.12
RPyC 3.0.6 has been released; fixes a bug in inspect_methods
2009.04.09
RPyC 3.0.5 has been released; fixes a bug in the forking server.
2009.03.31
A developerWork article by David Mertz!
Development Blog
New Security Layer (1248515179|%c)
Thread issues (1248249025|%c)
Approaching 3.1.0 (1248603367|%c)
I'm back (1243764403|%c)
Going abroad (1241211860|%c)
Welcome
RPyC (IPA:/ɑɹ paɪ siː/, pronounced like are-pie-see), or Remote Python Call, is a transparent and symmetrical python library for remote procedure calls, clustering and distributed-computing. RPyC makes use of object-proxying, a technique that employs python's dynamic nature, to overcome the physical boundaries between processes and computers, so that remote objects can be manipulated as if they were local.
Features
- Transparent access to remote objects; program remotely as if working locally
- Symmetric protocol, where both the client and server can serve requests (which allows, for instance, to use callbacks)
- Synchronous and asynchronous invocation
- Platform-agnostic: 32/64 bit, little/big endian, Windows/Linux/Solaris/Mac… access objects across different architectures.
- Capability based security model
- Integration with TLS/SSL and inetd
Use cases
- Excels in testing environments
- Control multiple hardware or software platforms from a centralized point
- Access remote physical (hardware) resources transparently
- Distribute workload among multiple machines with ease
- Implement remote services (like SOAP or RMI) quickly and concisely (without the overhead and limitations of these technologies)
See more use cases.
Learn RPyC in 20 minutes
If you are new to RPyC, check out the screencasts and the tutorial — these should get you started in matter of minutes. Full documentation can be found under the docs menu on the top navigation bar. If you can't find the answers you're looking for on this site, please post them on RPyC's mailing list.
 |
 |
|
