Why the Ping Loop Did Not Crash Wordpress

SIERRA MADRE, CA - MAY 29:  Seventieth anniver...Some days ago I did the Ping Loop Test and I luckily had only 4 duplicate posts to clean up. Now the question is, why did the loop stop. To answer this i didn“t have to go into analyzing logfiles and plugin behavior.

Ping.FM has rate limits of 3 messages per rolling minute to prevent spam. This absolutly makes sense for a message distribution service like them. And it does not just prevent spam but it also prevents fast loops that could crash a service.

This gives strength to the theory, that the probability of dangerous and fast inter-serviceĀ  “Ping-Pong-Like” API loops is is quite small. Most of the API Service providers will have restrictions on message count per time frame per client.

There might be more danger potential for more chain reaction like loops, where incoming messages come from different clients/services. We will see how the ongoing Api-Madness experiments will evolve…

One Response to “Why the Ping Loop Did Not Crash Wordpress”

  1. James Says:

    Hi, I found your blog on this new directory of WordPress Blogs at …. I dont know how your blog came up, must have been a typo, i duno. Anyways, I just clicked it and here I am. Your blog looks good. Have a nice day. James.


Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>