Say I have three databases: A, B, and Modules. I want to be able to deploy changes to all three and have the changes all commit (or become active) at the same time. I may have new config files that only work with the new code going into Modules so I don't want to put the config files in A and then afterwards insert the new code in Modules because there may be a gap in time where the config files and the code are not the right versions for each other. I don't want to have any downtime so stopping the server is not really any option. How can I insert my new files across the DBs and have the changes take place simultaneously? Perhaps I can have the app run at a particular timestamp and then insert all the new files and then remove the run-at timestamp. I'm not sure this works for the Modules DB though. Another option may be to put version info in the XML files in database A, then write the new code in the Modules DB under a new directory and write the code to only use the files in A with the new version, then change the modules root of the app server to the newer code dir (thus automatically only using the new version of files in A). I'll take "within a few microseconds" if "simultaneous" isn't really possible. Anyone know how to do this? Thanks! -Ryan
_______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
