On Fri, Mar 4, 2011 at 3:16 PM, Tomer Filiba <[email protected]> wrote:
> yes, well, i haven't heard of execnet either, but it looks more like a > competitor of the new multiprocessing module. > > on the PR front, it's better to compare how simple rpyc is, versus the > alternatives: > * pyro - complicated setup (requires name servers, etc.) > * xmlrpc - very limited scope > * soap / wsdl - overly complicated, slow, bloated > * multiprocessing - limited scope (doesn't have proxies, etc.) > * execnet - from what i read, it seems to aim at remote code execution. > rpyc doesn't aim there. > Regarding multiprocessing, on systems without fork (such as Windows) it attempts to "fork" by starting a new Python process and re-importing everything. If any import does non-trivial stuff this fails miserably. So multiprocessing's cross-platform support is problematic. - Tal
