Extending nameserver

[bpatzak]

We are interested in extending nameserver functionality. In particular, registering the multiple instances of same class and letting nameserver to generate unique name for them. The idea is to use metadata that will use class name as a metadata attribute allowing to get list of all instances. The new method will generate and return unique name for new class instance, something like classname.#n, where #n is unique id of instance. Hopefully we can do this outside Pyro on our side simply by creating a derived class form NameServer class. I wonder to know if there is any potential drawback of doing it like this.

Thanks,
Borek

[irmen]

I think it's fine? and basically what the "distributed-computgin3" example also does, among others? https://github.com/irmen/Pyro5/tree/master/examples/distributed-computing3

No nameserver modificaton needed at all

[bpatzak]

Thank you for pointing to example that I was not aware of. The example relies on client to generate unique names. I would like to ensure consistent, unique name generation on nameserver side, that is why I consider extending NameServer class.