Well, now that I have basic versions of ComeBack and remote post working, I had a few thoughts about Inter-Blog Pings in general.
There seem to me to be a few different types of pings now:
- Update pings
- Trackback pings
- Pingback pings
- ComeBack pings
- remote post pings
Doesn't it seem time to provide a common API for all these? Or at least unify all the code for them in a single Perl module. Trackback code is all over the MT core at the moment (at least as far as I've seen). In MT.pm and MT/App/Trackback.pm mostly.
It would make more sense to me to have something like the following:
That way all of the inter-blog communication code could be encapsulated in this Ping.pm module, allowing the easy creation and modification of pings. All the remotepost.pm module would have to worry about is posting the actual entry to the blog. It would not have to go through all of the steps needed to parse out the parameters from the HTTP Query string. And along those lines, this would also facilitate moving to another form of inter-blog communication. If you wanted to go XML or the like, just make the changes in Ping.pm and everything is wondeful in the land of pings again. Nothing to change in any of the other files.
Well. those are my thoughts for now at least.
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
Bloody good idea
Come to think of it, instead of just moving to another interface, you could actually add interfaces. That way you could send a (Update|Trackback|Pingback|ComeBack|Post-It) ping via (XML|HTTP|Email|Interface-of-the-future) and the base Ping.pm module would handle all the comms.
please send me the implementation of ping in linux
please send me a copy of your ping implementation as early as possible.
thanking you
i am student of Walchand college of sangli ,maharashtra i am also in search of IPv6 ping implementation so if u got any prgm. keep ur self in touch