From: Andrew T. <ajt...@hi...> - 2006-07-23 01:03:59
|
I think we also need to start a database of violators of bad feed production. :) Do the feeds all validate? If so, seems like a failure in the standard that doesn't specify what should be the content link vs. feed link vs. guid. Thanks Kevin, Andrew On 7/21/06, Kevin <ke...@dr...> wrote: > > > On 7/20/06, Kevin <ke...@dr...> wrote: > >> > >> current logic to get the value for link. I know it needs to be changed > >> 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 hash > for the item.(md5 or sha1) This will separate the link and uniqueness > concerns and make everyone happy. > > -- > Kevin > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Fofredux-devel mailing list > Fof...@li... > https://lists.sourceforge.net/lists/listinfo/fofredux-devel > -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |