Martin Cooper hinted at infra not liking it but didn't really give me a reason why. Mirroring for European users is the first explanation I have heard for this. From a project perspective I think the zone is superior. After all, we have much more control and we *don't* have to wait for our changes to mirror (a real PITA when making a crucial change - say to a download page during release time.)
That said, we could certainly continue on minotaur. I just don't think the response times for Europe would make up for the complexity of maintaining two sites (one in minotaur and one in the zone) and the reduced control (like the occasional permissions problem.) Sean On 1/8/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: > > > On 1/8/06, Sean Schofield <[EMAIL PROTECTED]> wrote: > > Bruno, > > > > I'm moving this discussion to the list. Others may have something to > > contribute here ... > > > > I think for now we will publish the site to the zone. At least until > > we're ready to switch to the mavenized site. Then we can discuss > > whether we want it on minotaur or the zone. Don't worry about the > > exact location for now. > > That (having the website on the zone machine) is not going to be popular > with the infra folks, and for good reasons. They'll want the static > websites (Maven generated or not) to be on minotaur, and appropriately > mirrored to ajax when necessary. > > It's perfectly reasonable for the static website to *point* at demos and > live running examples on the zones, but the website itself should be where > the rest of them are, complete with the mirroring onto ajax for European > users. > > Craig > >
