Interesting. How about creating a zip (The same way we zip up stuff during sharing) and put it into the registry? This will make sure that everything is persisted including custom UI, files created and so on. Everything that you need to persist.
I'd like to keep this as a configuration parameter, where this will be disabled by default and will be enabled by the user depending on the need. Thanks, Keith. Jonathan Marsh wrote: > At a customer meeting, an interesting requirement came up. The customer has > geographically-distributed backup systems, and in order to provide fail-over > support they don't keep any state on the middle tier. For the mashup > server, we could plug in the remote registry and keep the mashup code, > comments etc. remotely. But I imagine this isn't a complete snapshot of the > state of the server. For instance, are the custom UI files saved in the > registry? Files written with the File object? Included files? Is there a > combination of improvements we can make to the mashup server, and > constraints we could document for the user (e.g. don't use the File object) > that would eliminate any critical state from the middle tier? > > > > Jonathan Marsh - <http://www.wso2.com> http://www.wso2.com - > <http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com > > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mashup-dev mailing list > [email protected] > http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev _______________________________________________ Mashup-dev mailing list [email protected] http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
