By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,173 Members | 796 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,173 IT Pros & Developers. It's quick & easy.

Re: Multiprocessing vs. [Pyro, RPyC]

P: n/a
sk**@pobox.com wrote:
>
JeffreyWith the release of multiprocessing in Python 2.6, is there
any Jeffreyreason to use Pyro or RPyC?

As far as I know the multiprocessing module only works on one machine
(multi-cpu or multi-core), not across machines.
So I thought at first, but then I saw this statement in the documentation:

It is possible to run a manager server on one machine and have clients use
it from other machines (assuming that the firewalls involved allow it).
--
Jeffrey Barish

Nov 14 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Jeffrey Barish <je*********@earthlink.netwrites:
sk**@pobox.com wrote:
>>
JeffreyWith the release of multiprocessing in Python 2.6, is there
any Jeffreyreason to use Pyro or RPyC?

As far as I know the multiprocessing module only works on one machine
(multi-cpu or multi-core), not across machines.

So I thought at first, but then I saw this statement in the documentation:

It is possible to run a manager server on one machine and have clients use
it from other machines (assuming that the firewalls involved allow it).
Depends. I don't know much about the multiprocessing module in 2.6,
but I have built a distributed application on Pyro.
Pyro has many advantages -- a query-able name server, GUI tools for
monitoring your setup, and remote agents. It is also rather simple in
comparison to other similar tools (*cough*twisted.pb*cough*). However,
it is essentially an RPC style system, so some people might not be too
comfortable with it. YMMV.
Nov 16 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.