Inheritance diagram for IPython.kernel.enginefc:
Expose the IPython EngineService using the Foolscap network protocol.
Foolscap is a high-performance and secure network protocol.
Bases: object
Adapt a RemoteReference to an IEngineBase implementing object.
When an engine connects to a controller, it calls the register_engine method of the controller and passes the controller a RemoteReference to itself. This class is used to adapt this RemoteReference to an object that implements the full IEngineBase interface.
See the documentation of IEngineBase for details on the methods.
See if a returned value is a pickled Failure object.
To distinguish between general pickled objects and pickled Failures, the other side should prepend the string FAILURE: to any pickled Failure.
Return the Engines id.
Return the Engines id.
Older version of pushSerialize.
Set the Engines id.
Bases: foolscap.referenceable.Referenceable, object
Adapt an IEngineBase to an IFCEngine implementer.
This exposes an IEngineBase to foolscap by adapting it to a foolscap.Referenceable.
See the documentation of the IEngineBase methods for more details.
Bases: zope.interface.Interface
Interface that tells how an Engine sees a Controller.
In our architecture, the Controller listens for Engines to connect and register. This interface defines that registration method as it is exposed over the Foolscap network protocol
Bases: zope.interface.Interface
An interface that exposes an EngineService over Foolscap.
The methods in this interface are similar to those from IEngine, but their arguments and return values slightly different to reflect that FC cannot send arbitrary objects. We handle this by pickling/ unpickling that the two endpoints.
If a remote or local exception is raised, the appropriate Failure will be returned instead.