Now that my
Keithba
synthesized feed is getting 40 hits an hour, I decided to
convert my cgi to a cron job.
What does this mean to you? On the plus side, responses will be
quicker. Futhermore, if you aggregator supports ETag headers or
HEAD methods, then less bytes will be downloaded. On the minus
side, since the data is cached, the results may be up to 15 minutes
time delayed.
Of course, you can always get the latest Keithba
here.
And now if you could get Joe on Software in an RSSFeed life would be splendid!
Anonymous: I remember the comment. Both servers certainly can stand the load of 40 hits an hour. I have just been scouring my logs debugging my caching logic, and this was simply a bit of cleanup.
FYI: before this rewrite, every response to every request for any page off of this site (including my various RSS feeds) was dynamically generated.
Dare: I've entered this comment using preview (twice) on IE on WinXP. My name and URL seems retained. Can you tell me exactly what steps you performed, and the state of the Remember info checkbox below?
Ah, the irony. A well respected developer who specialises in XML uses blogger.com for his blog and so doesn't have an RSS feed. So a friend scrapes the html to produce a feed which then gets lots of hits and needs cacheing.
This is fixing the leaky roof by buying more buckets isn't it?
Seriously though folks, we ought to be pushing Blogger to produce native RSS for all it's blogs now they have Google behind them.
As a complete aside, are there any native Dotnet equivalents of things like Movable Type?
I don't know if there are any equivalents to MovableType in any language, but there is weblogging software out there written in/for ASP.NET. and/or Exchange and/or SQLServer.
I had a weblog powered by pencil and paper once, but the bandwidth bills at Kinkos and the post office were killing me. Now I lovingly hand-code my weblog in HTML, which is fine most days, but the angle brackets are sharp and pointy, and make it difficult to have bowel movements.