[Zope3-Users] Re: How to distribute distinct components among multiple Zope servers?
Chris Withers [EMAIL PROTECTED] writes: Reinhold Strobl wrote: For instance, server A provides the views and server B provides business functionality via utilities. As a side effect, this should help to increase scalability, since I split functionality over multiple servers. But how to I get them to work together? Is XML-RPC the right/only solution? Have you looked at ZEO? I've used the pattern of a backend server pumping content into a zeo storage server to be served out through an app server for years on one major project and that sounds like it'd work for your requirements above. cheers, Chris Thanks for your reply, but I have looked on ZEO - however: this technology only allows a seperation of application from the concrete storage. But what I am looking for is I want to seperate the application tier itself. For instance, I have got two utility components serving different functionality. But I want to distribute those components among two servers, but they should stay reachable from each other... Thanks! ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: How to distribute distinct components among multiple Zope servers?
Hi, On Wed, May 17, 2006 at 09:15:22AM +, Reinhold Strobl wrote: [snip] Thanks for your reply, but I have looked on ZEO - however: this technology only allows a seperation of application from the concrete storage. But what I am looking for is I want to seperate the application tier itself. For instance, I have got two utility components serving different functionality. But I want to distribute those components among two servers, but they should stay reachable from each other... Why not using ZeO + two Zope servers in front of it that both provide all the functionality? You can put a proxy server (don't forget to switch off the cache) in front of them. This proxy server then examines all request's urls and forwards them to the server resposible for the requested functionality. Remember: It's always better to have two identical systems and use it differently than to have two different systems. Regards, Frank ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Re: How to distribute distinct components among multiple Zope servers?
Reinhold Strobl wrote: Consider the followng example: one company has got a Zope application running on a single server. This applications need the components of e.g. the supplier of the component running on a different server. So I don't want to mirror both, because the both companies are more or less independent. So I assume the only possible is XML-RPC (with its limitations of restricted data types and so on)? I'm not a Zope expert, but to me it sounds like you want to solve a problem with Zope, which it is not intended for. If you want to implement complex distributed scenarios use SOAP, XML-RPC, CORBA, DCOM, ... or whatever suits your needs. Then you could still implement a thin Zope utility, which wraps access to such an service, to allow easy access from within a Zope application. regards, Achim ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: How to distribute distinct components among multiple Zope servers?
I'm not a Zope expert, but to me it sounds like you want to solve a problem with Zope, which it is not intended for. If you want to implement complex distributed scenarios use SOAP, XML-RPC, CORBA, DCOM, ... or whatever suits your needs. Then you could still implement a thin Zope utility, which wraps access to such an service, to allow easy access from within a Zope application. So, am I right, if Zope is mainly intended for (single) web applications and no distributed complex component architecture? ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] Re: How to distribute distinct components among multiple Zope servers?
On Wed, 2006-17-05 at 10:18 +, Reinhold Strobl wrote: I'm not a Zope expert, but to me it sounds like you want to solve a problem with Zope, which it is not intended for. If you want to implement complex distributed scenarios use SOAP, XML-RPC, CORBA, DCOM, ... or whatever suits your needs. Then you could still implement a thin Zope utility, which wraps access to such an service, to allow easy access from within a Zope application. So, am I right, if Zope is mainly intended for (single) web applications and no distributed complex component architecture? It sounds to me like you're trying to use Zope components in a fashion like J2EE components are meant (but rarely ever are) to run. J2EE will do it a little (but not much) more transparent than Zope will, but its quite doable with Zope. Running multiple Zope app server instances (like you would run multiple j2ee instances) and have the components communicate via xml-rpc (probably xml-rpc views) is pretty close to what j2ee does to communicate between components using RMI/CORBA. The advantage that j2ee has in this scenario is that most of the heavy duty j2ee implementations (weblogic, websphere, etc) support transaction handling across distributed components in a very flexible manner. It may be doable to construct something similar with Zope but I've not tried. - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
