Projects / SPyRO

SPyRO

SPyRO is a multilingual Object Request Broker (ORB). SPyRO uses the most efficient available connection between peers to minimize the costs of transport and parsing in the communication. SPyRO provides transparent and translucent remote object access.

Tags
Licenses
Operating Systems
Implementation

Recent releases

  •  14 Oct 2006 20:31

    Release Notes: Documentation updates and API updates were done. The default location was changed to /SPyRO?XMLRPC.

    •  10 Oct 2006 21:10

      Release Notes: The HTTP protocol is now supported by the HTTP Basic server, with customized methods. Now a complete HTTP server is included. There is a more flexible handler engine. CodePool now can import modules from modules. There are many bugfixes.

      •  16 May 2006 00:29

        Release Notes: General improvements to the shttp package, and minor bugfixes to the SPyRO and shttp packages.

        •  10 May 2006 06:25

          Release Notes: The authentication module is now separated from the SPyRO module, and the authentication modules are located in the PyRO.policies package as Authentication or Security policies. Many new policies and a new structure to easily create authorities were added.

          •  29 Apr 2006 03:57

            Release Notes: HTTP/1.0 requests are now closed in the server if keep-alive is not given. This changed the xmlrpclib.ServerProxy blocking behaviour in requests. Various XMLRPC enhancements were made in getAttr, setAttr, and callMethod. 'execute' and 'SPyRO_execute' now have default values.

            Recent comments

            15 Jan 2006 11:03 sadit

            Re: There is an easy to determine if an RPC library is broken
            This is true, but SPyRO support Pickle for trusted environments. If anybody plans to use SPyRO in untrusted environments it supports many other marshalers or serializers.

            Have a nice day

            > If the library employs Python's pickle

            > module, it is broken. Period.When will

            > people learn that pickle is not suitable

            > for this task? "Oh, it looks so easy."

            > "Oh, it's so fast, just look at those

            > objects fly." "Oh it will core my

            > process when handling a maliciously

            > constructed string, there goes my

            > server." "Oh, it allows arbitrary code

            > to be executed by a remote party, woops

            > there goes my credit card database."Wake

            > up. This is not news. The pickle

            > documentation explicitly points out the

            > fact that it is not intended to be used

            > in this fashion. Stop doing it. Stop

            > releasing software that does it. Just

            > stop, already.

            02 Nov 2005 21:18 kuran

            There is an easy to determine if an RPC library is broken

            If the library employs Python's pickle module, it is broken. Period.

            When will people learn that pickle is not suitable for this task? "Oh, it looks so easy." "Oh, it's so fast, just look at those objects fly." "Oh it will core my process when handling a maliciously constructed string, there goes my server." "Oh, it allows arbitrary code to be executed by a remote party, woops there goes my credit card database."

            Wake up. This is not news. The pickle documentation explicitly points out the fact that it is not intended to be used in this fashion. Stop doing it. Stop releasing software that does it. Just stop, already.

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.