Rael
Dornfest: I'm thrilled to announce the 1.0 release of my
Blosxom weblog
app.... With the choice of dynamic or static rendering, Blosxom is
at the point I'd hoped it'd be when it went 1.0.
Now I have my first dillema. I want to do static rendering for
scalability, but in accordance with the teachings of REST, I also
want my URI to identify resources that can serve both GETs and
POSTs.
Meanwhile, the temptation to ditch Perl for Python is
growing...
As a side note, you might have a look at your template for stories. If you go look at one (Cohesion, for instance), you'll notice the home link takes you to 0101679.
POSTs to my weblog are treated as comments or trackbacks. Posts can be done either via index.html specifying parent=1148 or directly via 1148.html - the difference being what is returned. From a human factors point of view, where do you expect to end up after you enter a comment? Early on, I decided to make this be the home page, and I have yet to hear a complaint.
The direction I would like to head is having one be able to post an RSS item, and that logic I would prefer to do in Python.
Yes, my stories are long overdue for a facelift.
Meanwhile, I am starting to have some serious doubts about this whole REST thing. ;-)
Yay! Rael Dornfest released Blosxom 1.0 today. Now I can convert my heretofore hidden movie log to something better suited...
[more]
Trackback from Christopher Elkins
at
Well after reading the post (no pun intended) that followed, I wondered if I had fallen for a joke :-) Amen to Python, BTW, I have been reading Dive Into Python, though with me, it's more like "Dip your toe into Python"
I've programmed in Perl for many years, but having written this with nothing more than a stock Python installation (using regular expressions, sax, sgml, xmlrpc), I've been impressed with Python.