I can see that this would complicate matters for mirroring websites, though it's not clear why you need to mirror websites. Obviously distributions/downloads can benefit from mirroring, and notebook servers can easily be loaded down, but I'm surprised that the main community website needs it, do you expect it to be that heavily loaded ? Heavily loaded sites are usually broken up so that the db(s), static and dynamic parts of the site are served off different machines, and extra servers are added where needed.
-Drew On May 14, 7:44 pm, mabshoff <[EMAIL PROTECTED]> wrote: > On May 14, 11:15 am, Drew <[EMAIL PROTECTED]> wrote: > > Djanogo seems to mandate a DB backend, so since the Sage website is > mirrored in various places I would greatly prefer not to depend on it. > It would likely mean the end of many mirrors since static packages > [generated via script] just work while db backends not only bring > consistency issues [and that includes sqlite - which sucks performance > wise for any set of data beyond trivial], but also increase the > required tools that need to be installed on the webmirror in question. > KISS is the guiding principle for Sage development and so should be > the website. But it doesn't have to look ugly :) --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
