Log message:
Delete py-foolscap; now in pkgsrc/net - thanks!

Log message:
Minor cleanup about INSTALLATION_DIRS and unused variables as
recommended by pkglint; no real change.

Log message:

	wip-changes:
	===========
	o Upgrade version --> 0.5.1
	o SET LICENSE
	o add dependdency: py-zopeInterface

Log message:

	pkgsrc-changes:
	--------------
	o remove specifications directory (containt some html files)

Log message:

pkgsrc
	o update 0.4.1 to 0.4.2
	o Added post-install procedure: containt 
	   Documentation
	o Added two script in PLIST 

Log message:
Update version

Log message:
Import py25-foolscap-0.3.2 as wip/py-foolscap.

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.