问题描述
大家好,
在工作中我正在考虑为我们的分布式
处理系统(基于网络的购物车)提供解决方案实际
印刷生产线)基于Pyro。我已经做了一些小的实验,而且Pyro看起来很有趣,并且像我想要的那样实现了很好的实现。我有几个问题:
1)有没有人对Pyro有过任何经验,如果是这样的话,你有没有任何稳定性?
任何稳定性或者内存使用问题在各个参与计算机上运行Pyro服务器或名称服务器
? (我们有一个混合的环境,那就是Linux和Windows的b
,但很快就会转向所有的Linux(RedHat)
环境。
2)我工作的其中一个人更倾向于在进程之间建立XMLRPC
通信,并且他对运行
守护进程也很谨慎。他的解决方案是基本上使用Python CGI代码
来响应各种XMLRPC请求。有人对此有任何意见吗?我知道我的已经是什么了。 :)
3)我考虑过使用CORBA,它功能更强大,而且肯定比b $ b更快,但设置起来很复杂与相当简单的工作相比,我试图做的工作似乎很禁止。有没有人有任何想法
这个?
提前致谢,
Doug
Hi all,
At work I''m considering proposing a solution for our distributed
processing system (a web based shopping cart that feeds an actual
printing production line) based on Pyro. I''ve done some minor
experiments with this and Pyro looks interesting and like a good
implementation of what I want. I''ve got a couple of questions though:
1) Has anyone had any experience with Pyro, and if so, have you had
any stability, or memory use issues running Pyro servers or nameservers
on the various participating computers? (We have a mixed environment of
Linux and Windows, but will be heading to an all Linux (RedHat)
environment soon.
2) One of the guys I work with is more inclined to set up XMLRPC
communication between the processes, and he is also leery of running
daemon processes. His solution is to have essentially Python CGI code
that responds to the various XMLRPC requests. Does anyone have any
opinions on this? I know what mine are already. :)
3) I''ve considered using CORBA, which is more powerful, and certainly
faster, but it''s complexity to set up compared to the rather simple
work I''m trying to do seems prohibative. Does anyone have any thoughts
on this?
Thanks in advance,
Doug
推荐答案
嗯,我确实在这里有优势,是Pyro的作者...... :)
- Irmen
Well, I do have an advantage here, being Pyro''s author... :)
--Irmen
这篇关于火焰稳定性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!