Irmen de Jong

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

Investigate where the time is spent. Sounds to me like a DNS lookup issue that blocks the program. I.e. a configuration issue on your windows installation. (since the ubuntu side...

"inside Pyro" is extremely vague. Most of what pyro does is calling the OS's network socket functions, for example. I suspect the locate_ns() call is not finding the name server...

Alternatively, you could try another one of the examples such as the "benchmark" one. It doesn't use a name server , so it may tell you if the delay is...

Pyro itself can also write a trace log file if you set the correct configuration options. But it seems Windows does something funky related to "localhost" ip resolution. Easiest probably...

what exactly was the issue you encountered initially?

Could you perhaps add a unit test for this change as well? I think test_daemon.py could be the right place for it.

Personally I prefer writing explicit adapter classes to have full control over what is happening, but I can appreciate some simple generic wrappers to get "the bulk done" if you...

Could you perhaps also add a unit test for this? I think TestServerOnce in test_server.py contains tests that check iteration and such

and PAL then as well perhaps?