The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Problem Tracking in BottomFeeder

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Problem Tracking in BottomFeeder Posted: Dec 1, 2005 8:40 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Problem Tracking in BottomFeeder
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

One of the things that fell out of BottomFeeder as we moved from the old network library (a hack job I created back in 2002-2003) to NetResources was error reporting at the application level. With the 4.1 release, that's back. If you pull down Help>>View Error Log, you'll see something like this:

Network nrspace=

What you see there is a list of errors that happened during the last few rounds of network updates. If you want to clear that, just hit the "Clear" button. If you want more details, hit the "Save to File" button - one of the results for the screen above look like this:

Time: December 1, 2005 10:53:25.358Description:NetResources Error: <<Net.HttpObjectNotFound (404 Feed not found error: FeedBurner cannot locate this feed URI. )>> on url: http://dwlt.net/tapestry/getfuzzy.rdf

Which tells me that when that feed was last queried, a 404 popped up. BottomFeeder treats a 404 as transient (there's a gone error - 410 - that Bf will use to mark a feed as dead). You might want to watch for repeated 404 errors though - it probably means that the site should have issued a 410.

Read: Problem Tracking in BottomFeeder

Topic: OO vs. Same old Stuff Previous Topic   Next Topic Topic: Missing the Threshold

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use