ROC - Remote Object Call
ROC is RPC enhancment allowing to manipulate remote objects like they are local
Why ROC?
ROC development was started to support acceptance testing of distributed systems with FitNesse, waferslim and vagrant System infrastucture may be described as follows:
Host machine running FitNesse server and SLIM server;
Set of guests, that are provisioned by vagrant with ROC servers;
When hosts’ fixture is invoked by SLIM server, it can access guests’ roc servers.
Usage
To start serving your modules on remote machine with ROC:
python -m "roc" -m <your-module-path> -p <port>
To connect to your instance from host:
from roc.client import server_proxy, remote_module proxy = server_proxy(host='127.0.0.1', port=1234) RModule = remote_module(proxy)
To instantiate object on remote machine:
remote_instance = RModule.RemoteClass(1, 2, 3)
From now every method called on remote_instance will be executed on remote.
When you finished, call proxy.shutdown() to, well, shut down remote ROC server.
Metadata
Release files for roc 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| roc-0.3.2.zip | 8.2 kB | Without provenance | Details for roc-0.3.2.zip |
Release files / roc-0.3.2.zip
| Download URL | roc-0.3.2.zip |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eae975177878a78e40d8c0295deae4741ea57829a1348ae064c9d29b7b0f6483
|
|
BLAKE2b-256 checksum How to use checksums |
830f02978327604ed29208ffcf2a07d5f1b7c93f3bbc1bf5321c3cadd26749d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for roc 0.3.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.