Friday May 02, 2003
|
Vanity Foul Dedicated to the wanderings of an egotistical mind. |
|
Re: The Ultimate Weblogging System Matthew has taken the time to respond to comments and everyone's comparison of their blogging system against his requirements. Thank you Matthew. But you still haven't explained the Creative Commons requirement. Is all you are looking for is the ability for the user to select a License and have the appropriate logo displayed? On a lighter note Found via Code Intensity. The Ultimate Weblogging System Via Sam Ruby, Matthew Thomas's list for the Ultimate Weblogging System. Truth be told, Roller has quite a long way to get there and won't ever reach the first requirement: GPL. That said, I'd like to evaluate Roller against the list anyway.
Where relevant, should I add links to the Roller JIRA issues where these requirements are documented?
Why you should love open source While I'm patting myself on the back, I might as well mention that I also contributed a fix to Velocidoc as well. This is what I love about working with "open source" (and others have said, likely better): If I find a problem, I can fix it myself! When I have a problem with Weblogic, all I can do is search the web for a workaround, or pray that BEA has released a patch that fixes it. While it isn't Open Source (notice the capitals), when I run into a problem with Resin I can open up the code and take a stab at fixing it myself. And once I do, I can post the bug/solution with Caucho and feel safe it'll be integrated into the next release. Why can't we all just get along? Jeremy Rayner reported an unfortunate bug against Roller, but it's not quite Roller's fault: we use LIMIT in our SQL to limit the results of some queries (most noticeably the Home page). But HSQLDB doesn't support "LIMIT #", unlike MySQL and Postgresql - you have to use TOP #. Of course, writing our persistence layer such that it knows what database you are using would be lame. In the course of my research into this problem I found wide inconsistencies in MySql, Postgresql, and Hsqldb (didn't look at the others). Read the comments in the bug report above and you'll see what I mean. So for the last couple days its been perculating in the back of my mind on how to fix this. Fixing it in Roller's code isn't appropriate, it's really up to the persistence layers (Castor & Hibernate) to address the differences in databases. In my research I had also come across a couple similar issues entered against Castor, and one proposed solution. That solution wouldn't address our problem, but after a day of simmering the answer came to mind. I'm really rather pleased with myself, which is the whole reason for this post. Hey, this is "Vanity Foul" after all. Roller needs ETag support Note to self: We added Last-Modified/If-Modified-Since support some time ago, to be complete we should add ETag support.
(
Apr 29 2003, 01:05:06 PM
)
Roller
Permalink
Re: Very Fricken Cool! I have to echo Matt here, what Dave has done to Roller's Wiki looks very good. Keep up the good work Dave! I try to contribute here and there, but you da man!
(
Apr 27 2003, 08:15:35 PM
)
Roller
Permalink
Help, I'm evil! Just as was Carlos, so am I
(
Apr 25 2003, 11:00:39 PM
)
Entertainment
Permalink
|
|
||||||