... continued

The BaseManager's register method takes in a number of parameters and it's important that we discuss how they are used. We'll explain each one of them below:

• typeid

• callable

• proxytype

• exposed

• method_to_typeid

• create_method

In the previous sections, we already discussed the first two parameters. We'll study the remaining using an example. Consider the following Pair class that holds two values x and y.

class Pair:
    def __init__(self, x, y):
        self.x = x
        self.y = y

    def get_x(self):
        # return self.x
        return fancy_type(self.x)

    def set_x(self, new_x):
        self.x = new_x

    def set_y(self, new_y):
        self.y = new_y

Let's say we want to register an object of this class with a manager so that it can be shared among processes. The most straight-forward way to register would be:

pair = Pair(5, 6)
manager.register('get_pair', callable=lambda: pair)

All the other register parameters will take on default values. The proxy returned for the pair would be AutoProxy and all the public methods on the pair object are by default available for consuming processes.

If you wanted to restrict the methods available to consumers you can specify the list of available methods using the exposed parameter. The register call would be as follows:

pair = Pair(5, 6)
manager.register('get_pair', callable=lambda: pair, exposed=['get_x'])

The above change would only make the get_x() method available on the pair object. The below runnable script barfs when we try to access set_x() ...