Quoting Aigars Mahinovs (aigarius@gmail.com): > I personally feel strongly that move to storing everything in a > database is long overdue in Pootle, but I am very cautionos about the > move because of respect to development decisions that Pootle > developers made before for reasons that I do not know at this point. > But I would really like these reasons to be brought up so this > technical decision can be discussed on real technical merits. I am a bit puzzled by this discussion. You guys all know that my technical skills, being what they are, do not allow me to judge the details of the discussion. However, my understanding is that the main intent behind the "separate backend from frontend" work is to allow further changes in implementations without redesigning the whole thing. In short, if a correct API is implemented for storage, then I guess that different storage modules could be hokked in this API to allow storage either in a RDBMS, or as flat file, or other possible storage methods for the data. Am I wrong? Otavio (I CC you to be sure that you see this mail), can you read the thread (in debian-i18n) which this message is part of, and then give your advice there (the thread is crossposted in the Pootle devel list)?
Attachment:
signature.asc
Description: Digital signature