diff options
| author | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
|---|---|---|
| committer | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
| commit | 4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch) | |
| tree | ba5f07bf3f9d22d82e54a462313f5d244036c768 /dev-python/foolscap/metadata.xml | |
reinit the tree, so we can have metadata
Diffstat (limited to 'dev-python/foolscap/metadata.xml')
| -rw-r--r-- | dev-python/foolscap/metadata.xml | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/dev-python/foolscap/metadata.xml b/dev-python/foolscap/metadata.xml new file mode 100644 index 000000000000..05b50f1ab47b --- /dev/null +++ b/dev-python/foolscap/metadata.xml @@ -0,0 +1,28 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> + <maintainer type="project"> + <email>python@gentoo.org</email> + <name>Python</name> + </maintainer> + <longdescription> +This is a ground-up rewrite of Perspective Broker, which itself is Twisted's +native RPC/RMI protocol (Remote Procedure Call / Remote Method Invocation). +If you have control of both ends of the wire, and are thus not constrained to +use some other protocol like HTTP/XMLRPC/CORBA/etc, you might consider using +Foolscap. + +Fundamentally, Foolscap allows you to make a python object in one process +available to code in other processes, which means you can invoke its methods +remotely. This includes a data serialization layer to convey the object +graphs for the arguments and the eventual response, and an object reference +system to keep track of which objects you are connecting to. It uses a +capability-based security model, such that once you create a non-public +object, it is only accessible to clients to whom you've given the +(unguessable) FURL. You can of course publish world-visible objects that +have well-known FURLs. +</longdescription> + <upstream> + <remote-id type="pypi">foolscap</remote-id> + </upstream> +</pkgmetadata> |