Joern Nettingsmeier schrieb: > Andreas Hartmann wrote: >> Jörn, >> >> Jörn Nettingsmeier schrieb: >> >>> the blog publication is a really bad example of cheating users into >>> believing we can do blogs. i think it should go. all it currently does >>> is show that neither our sitetree browsing nor our repository access >>> scales very well. >> >> I don't quite understand this - why does the blog publication show >> particular drawbacks of the sitetree / repository scalability? > > well, maintaining a big blog is a bit of a nightmare. i must confess i > haven't checked the blog in a while, but i tried to use it seriously a > few months back, and it would totally collapse when you have a few > hundred articles in it. especially browsing them was a nuisance. but > it's probably not really a repository thing... sorry for this off-hand > remark, it was inaccurate.
Well, maybe it is really a repo problem. It would be great to have some stress tests in the SVN. Did you add the articles manually, or do you have a test environment to reproduce the problems? >>> our content repository is document-centric and allows for >>> arbitrary xml. >>> that's good. blog content is simple and belongs in a database. >> >> IMO a blog isn't an atypical Lenya application. >> The major problem I see is that the blog publication contains >> a lot of complex legacy code. It would be great if we could simplify >> and modularize it to improve the maintainability. > > we should withdraw the blog from the rc (at least mark it as > work-in-progress and hide it from the welcome screen) and clean it up > thoroughly before announcing it as part of a lenya release. the last > time i checked, it was neither stable nor had the minimum feature set of > a true blog, and it is certainly not on par with the rest of lenya. +1 I don't have a good feeling about releasing the blog in its current state either. I did some testing and bugfixing, but the amount of bugs which occured somewhat discouraged me. What do the others think? -- Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
