From e334c472fb4be44feec3a73402fc4a2b062cbfc0 Mon Sep 17 00:00:00 2001
From: admin Receiving Trackbacks is a little more complex than sending them, only because you will need a database table in which to store them,
and you will need to validate the incoming trackback data. You are encouraged to implement a thorough validation process to
guard against spam and duplicate data. You may also want to limit the number of Trackbacks you allow from a particular IP within
-a given span of time to further curtail spam. The process of receiving a Trackback is quite simple;
+a given span of time to further curtail spam. The process of receiving a Trackback is quite simple;
the validation is what takes most of the effort.
Your Ping URL
@@ -132,7 +132,7 @@ the validation is what takes most of the effort.
Your Ping URL must point to a controller function where your Trackback receiving code is located, and the URL -must contain the ID number for each particular entry, so that when the Trackback is received you'll be +must contain the ID number for each particular entry, so that when the Trackback is received you'll be able to associate it with a particular entry.
For example, if your controller class is called Trackback, and the receiving function is called receive, your -- cgit v1.2.3-24-g4f1b