If your talking about changes on the application level, if zodb is your datastore, this would be appropriate. You can read more on zope wiki about zeo to get help. Since you are concerned about shutting down a single server I am assuming your setup is not large.
Large setups would most likely be load balanced across multiple instances per server and over more than a single machine for availability. This provides other possibilities that include diverting requests from the application server you are maintaining such as temporary changes on balancer or DNS (in case of round robin DNS setup) for example. These days, it can also mean just firing up another server with the improvements to take load and killing off the one that would otherwise need maintenance. If your talking about changes at database level, this depends on the datastore, and technologies your are using for replication and backup. Don't think this helps much since its pretty generic answer. You might also find some reading in plone docs I believe about system maintenance for zope - so this might be another place to look, or in a plone book for that matter. Regards, David hass wrote: > Hello all, > > I did some extensive Z3 2 year ago and now I am warming up to get into > the pool of z3 again. > > I was wondering if there was any way in z3 not to shut the whole program > down when code maintenance is needed. > It wold be like having a simple instance run in the background which can > do the basics, and then other functionalities plug into it as different > z3 instances. > so when one needs to update the code in one part, it can only shut the > responsible program (instance) without shutting the whole web server. > > I googled a bit and thought maybe by having multiple instances which > share a database through ZEO and apache's rewrite module to redirect > change the port based on the URL, I can bundle something up but that > doen't seem so elegant I suppose. > Is there a more standard way to do this? > What do z3 experts do when they have a big server with many logically > seperate functionalities and they want to update only one of them, plus > they don't want to have down time for the whole server. > > Any help is greatly appreciated. > Hass > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Zope3-users mailing list > Zope3firstname.lastname@example.org > http://mail.zope.org/mailman/listinfo/zope3-users
_______________________________________________ Zope3-users mailing list Zope3email@example.com http://mail.zope.org/mailman/listinfo/zope3-users