From: Kevin <ke...@dr...> - 2006-07-21 16:21:14
|
> On 7/20/06, Kevin <ke...@dr...> wrote: >> >> current logic to get the value for link. I know it needs to be change= d >> to >> make it work better, but I don't know how. > > Thanks for showing the root of the issue. I would think the first step > would be to re-order the priority of how a link is obtained. First if > there is a "link", use that, then the enclosure url perhaps, and > finally the GUID. > > I agree that I didn't really realize the possible problems either > before. GUID was typically URL since that has to be unique. HOwever, > the GUID doesn't *need* to be the URL. Right, I'm the one that changed the link resolution order to favor GUID tag over the LINK tag. There was a feed where the link tag was constant for all items, but the guid was a unique URL. I plan on adding an indexed column to the item table to hold a unique has= h for the item.(md5 or sha1) This will separate the link and uniqueness concerns and make everyone happy. --=20 Kevin |