SoandSo.net

jeolee님과 eouia님의 글을 읽고도 감을 잡을 수 없다. MT에는 pingback이라는 것이 없어 test를 해 볼수도 없고...

인터넷에 올라와 있는 관련 글들을 읽어 보아도 '바로 이거다'라고 단정을 내리기가 어렵다. 이쪽 계통은 일자무식이라 글을 읽어 보고도 개념잡기가 힘들고 결정적인 것은 짧은 영어 실력 탓에...

• Whitepaper: Pingback vs Trackback
• Autodiscovery and the death of TrackBack
• Pingback vs. Trackback, Autodiscovery in MT 2.5

in-depth한 구조적인 차이점은 둘째치고 그 차이를 이렇게 이해해도 될런지? 누가 명쾌한 답 좀 내려주었으면 좋겠다.

When you send a TrackBack ping, you are saying 'I responded to this, and I think that your readers would also like to read what I said.'

When you send a PingBack ping, you are saying 'I linked to you', nothing more.

In the pingback model, the client does the work of finding the pingback server, and then invokes a simple XML-RPC call to that server with the two URIs.

In the Trackback model, the client has to do all the work of finding the trackback server, which includes mapping the permalink to the trackback ID by parsing some RDF. The client then has to call the server using the constructed URI, which then (depending on the implementation) has to map this ID back to the permalink.

You can pingback any document, even plain text files, images, and files which do not know that pingback exists, so long as the document can be served with a pingback HTTP header. Due to its use of RDF, trackback can only correctly be applied to XHTML documents sent as text/xml, application/xml, or (maybe at a pinch) application/xhtml+xml, and, if you are ready to violate the standards, to HTML or XHTML documents sent as text/html.