Part of Bill's incredibly stupid web diary. Read some more today, yerhear!
|
Nearly all the high profile diaries have prolonged periods of inactivity. This incredibly low profile diary is no exception. Last time there was a big delay, it was because I was spending my spare time (as short as it is) on developing BISHOP, the software which generates all the files you see before you.
Before that time, my diary system was broadly just copying a template file and editing the index page. Fine for a few articles, but it was clear the system would not be scalable and that some automation would be required.
So between August and November 2002, instead of spending the few moments of time on writing articles, I wrote BISHOP instead. It took a directory full of text files and a template file, and generated a bundle of static HTML files which I could upload to my web server.
I've now since decided that CGI generated HTML is the way to go. Yes, a complete reversal of my previous stance.
A big problem is the storage of this "directory full of text files". At the moment, I carry a floppy disk full of files around with me, which also doubles as my CVS archive. If I keep this diary-ing up, I'm going to run out of space sooner or later.
Before, my chief worry was the CGI overhead becoming overwhealming in the face of a slashdot effect. I've since concluded that the limited capacity of the network will be the problem, long before the CGI starts running out of time. But not to go overboard, I'm developing BISHOP Mk II in C++, using the lightweight GDBM database system to store my articles. At least I could avoid the overhead of running a Perl or PHP interpreter.
"But why not just use an existing Blogging package?" I hear you say. Well, I'd like to practise some real-world CGI, and a diary seems an inoffensive way to start trying. My CGI work to date has only been fun stuff on an isolated server. No possibility of external operation. Now, I'm going to have to deal with the might of various attackers and other nasty people. I'd like to make mistakes on this thing rather than the next great project I have in mind.
If the slashdot effect ever comes my way, I'll know if I took the right step or not.