King Ping provides a similar service to sites like Ping-O-Matic, which accept a blog URL and notify sites like Technorati that an update has occurred. Not everyone needs these services anymore as the process is often automated, but for those who do, King Ping gives you a nice Ajax interface for it.
The application uses Multi-Stage Download – an XHR request is uploaded for each engine to be notified. The King Ping service at the other end then acts as a Cross-Domain Proxy, routing the call toward an engine and passing back the result to the browser. In the web page’s results area, there’s a designated status area for each engine, which gets filled as soon as the browser receives the corresponding response.
Joe Anderson, who “pinged” us about it, says there are still issues with King Ping.
King Ping’s AJAX runs very smoothly, though I don’t like the fonts and colours used throughout the site. For some reason, I find the constant use of grey quite depressing; and I think a nice blue gradient would revamp the site.
King Ping has a few other faults. It claims to be able to ping BlogShares, but in fact it can’t. BlogShares RPC is only available to approved parties (Pingoat and Ping-O-Matic), so BlogShares refuses connections from anyone else. Another fault is it doesn’t provide an RPC. This stops you adding it to your blogging software to automatically ping after each update. Ping-O-Matic and Pingoat, however, do offer RPCs.