On Jun 30, 2008, at 9:56 AM, Axel Gembe wrote:
> > Noah Kantrowitz wrote: >> -1 on this whole patch set. Trac already can't handle simple >> replication, so all this added complexity is for pretty much nothing. >> This would also be yet another global break for very little gain. >> > Replication is a function of the database, not Trac. Trac just has > to be > able to direct its writes to another database. > I have a fully working replicated multi-project Trac set up with these > patches, which is a *big* gain in my opinion. > You could also use multi-master replication to do this, but I have a > strong dislike for the existing solutions. > Anyways, I certainly don't need this to be applied badly (although I'd > like a solution in the long run) because I can maintain my own branch. No, there are things we do not store in the DB. The major issues are attachments, config data, and VC data. While I suppose you could put all of those (really the whole Trac env folder) on a network file system, this still isn't true replication. I don't know of any good filesystem replication systems that don't cost $$$$$. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
