Christopher Warner

So, more work with Krang. There are alot of use cases where Krang fails or can be improved upon, for instance.

1. It’s startup/shutdown procedure is subject to race condition
2. If an editor is working with Krang and you shut it down it doesn’t save session. So basically if an editor is working and hits “Publish” at the very same time you’ve decided to shutdown Krang? They’ve lost all their work. They aren’t very happy when this happens.
3. The functionality called “Save and Stay” similar to “Save and Continue Editing” via Wordpress is pointless to have in my opinion. It should autosave every “X” minute(s)
4. When Krang fails? It fails; there are croak() statements through out the code
5. If someone writes an Element add-on that overrides a piece of core Krang functionality; lets say extending the publish routines and something goes wrong. Krang fails.
6. When you shutdown Krang and someone tries to access the content mangement system; they get an error message instead because no web server exist. This leads to confusion; instead the application server should shutdown but keep the webserver up that displays a user friendly message noting the system is down for whatever reason.
7. There is no data compression; being able to compress older material would be nice. Having it compressed and still available; with decompression on the fly would be nice (maybe via hardware as the data increases over time)

There’s more but those are some off the top of my head. I’m going to sit down and come up with use cases for every possible thing that can go wrong and fix those things in order. I won’t be doing this against Krang cvs or svn as we don’t use the latest version.

This entry was posted on Thursday, June 14th, 2007 at 4:34 am and is filed under Advogato, Commentary. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.