Quote:
Originally Posted by kiklop74
This is a classic case of obfuscated links. But let me explain few things first. This January Kovid and myself exchanged several mails regarding problem related to slow feed download. After some experiments I found out that the main culprit was the usage of obfuscated links from feed.
|
I'd like to pick your brain a bit on this subject. IIRC, (I haven't' worked on recipes in a while), the obfuscated link problem is solved by setting up a browser inside the recipe, and having the browser "click" on the obfuscated link, then feeding the results back to the recipe (by writing it into a local file) for further processing.
Quote:
The solution was to update default implementation of get_article_url to take into account not only link tag but also feedburner:OrigLink which (if exists) contains the real non-obfuscated link.
|
Having looked at miscellaneous information about feedburner, I think this tag may exist in the data the recipe receives from the RSS feed. Are you saying that get_article_url was rewritten to find and use this link in cases where the link tag was missing? Basically, just an improvement in the underlying method of obtaining the link which would previously have required using obfuscated link retrieval methods?
Quote:
However this solution does not cover all cases. Sometimes feeds do not have origlink tag but instead use guid tag.
|
I'm really not that familiar with the content of RSS feeds, but I've seen the guid.
Quote:
In those cases a recipe developer should override get_article_url and read the value of guid tag.
|
Why wasn't get_article_url rewritten to pick up guid if both the origlink and links were missing?
Thanks (in advance) for filling in some blank spots for me.