Browse > Home / Blog / Blog article: Cocktail Naplin to Startup (DIY Part Ten)

Cocktail Naplin to Startup (DIY Part Ten)

June 30, 2006

This is part nine of a series of posts describing how we are taking an idea from a cocktail napkin and putting into the real world. Start now, or read along from the start with: part one, part two, part three, part four, part five, part six, part seven, part eight and part nine.

Now that our plugin is almost completed (still waiting on Ryan King to bless the markup) we need to finish the hResume ping server. Ping servers are normally associated with blog authoring tools that automatically ‘ping’ a server with an XML-RPC signal. That ‘ping’ server then generates a list of blogs that have new material and distributes that information to various search engines and web-services. We plan to use the same idea for microformats.

Last year we built a ping server for Weblogs Work clients called QwikPing. It is based on Matt Mullenweg’s RSS Ping Version 1.0 standard. Our plan is to hire a coder (on contract) to reskin the QwikPing code to accept pings from our hResume plugins. The URI of our non-existant hResume Ping Server is already baked into each plugin. Each time an hResume is created or updated our servers will be aware of it. We can then pass that data along to anyone who would be interested that someone updated their resume. Below is the wireframe:

Written by Alexander Muse · Filed Under Blog 

Comments