Asynchronous Weblogs.com Pings

Hey, Dave Winer — how about implementing a method of invoking the weblogs.com ping that doesn’t do an immediate site check? It could just return a success code, then queue the request for processing. A cron job could then reap the queue every few minutes in an efficient multi-threaded way, and add the legitimately updated sites to the list.

This would eliminate the long wait and the associated timeouts for pinging clients, and hopefully would also reduce load on the weblogs.com server as well, since you would be able to pool database accesses.

You would, of course, still leave the original method available, for those who just can’t stand the thought of waiting more than one minute for their site update to be seen by the world.

Hmmm…. Of course, I doubt that Dave Winer is going to see this, since I’m tracking back to LazyWeb, and Winer and Ben Hammersley have a blood-feud going.

Related posts:

1. Bogus blo.gs pings?
   " Has anyone else noticed that blo.gs seems to be reporting erroneous site updates? Over the last day or so, it keeps reporting site updates,..."
2. blo.gs: hook up a cloud
   " Extreme technical blogging geekout zone ahead! blo.gs: hook up a cloud the old cloud service that operated via rebroadcasting pings over HTTP is being..."
3. Another nifty use for FOAF
   " Ben Hammersley has taken an idea of Dave Winer’s and added a cool twist to it: Using FOAF For Comment Identity and Followups. I’ll..."
4. Theme Issues
   " I am aware that there are some glitches in some of the themes, particularly when viewed in Internet Explorer. I’ll try to fix them..."
5. Open Source to the Rescue
   " Hurray for Open Source projects. At my work, we recently underwent a major system change behind the scenes (moved our line-of-business from a mainframe..."