Alt.Binz forum

New Alt.Binz versions => Requests => Topic started by: tvholic on September 30, 2008, 05:46:30 pm

Title: Notify on search engine failures
Post by: tvholic on September 30, 2008, 05:46:30 pm
If a search fails because the search engine is down (ie, timed out), there should be some sort of status message displayed so we don't keep retrying with different search terms.
Title: Re: Notify on search engine failures
Post by: Mystic2010 on September 30, 2008, 06:32:59 pm
Don't know about the other engines, but Newzleech either displays 'Error during transfer' or something a like over here..
Title: Re: Notify on search engine failures
Post by: tvholic on September 30, 2008, 07:21:46 pm
Newzleech either displays 'Error during transfer' or something a like over here..

Really?  Because Newzleech is down right now, and I'm not getting anything (using version 0.28.2).
Title: Re: Notify on search engine failures
Post by: davidq666 on September 30, 2008, 07:34:39 pm
your not looking in the right place. it doesn't appear where the results would be or on the search button but on another task-elements in the tab... look around...
Title: Re: Notify on search engine failures
Post by: tvholic on September 30, 2008, 10:51:54 pm
your not looking in the right place. it doesn't appear where the results would be or on the search button but on another task-elements in the tab... look around...

Okay, I see it says "Aborted" in the status field.  So I'd suggest there should be a "Failed" or "Timeout" status to distinguish it from a user-initiated abort.  Also, I think the status field should change while a search is running, instead of showing the status of the previous search.
Title: Re: Notify on search engine failures
Post by: Hecks on October 01, 2008, 12:01:24 am
It doesn't show 'Aborted' here, but 'No results'.  This is obviously dependent on the status codes received from the site and - because currently it's a DNS issue with Newzleech - which DNS servers you're using.  OpenDNS redirects to OpenDNS guide, for example, so Alt.Binz receives a page, just not one with any recognisable results.  Usually the error messages are unambiguous.

Anyway, 5 seconds with your browser is enough to see what's really going on.  It's hardly deal-breaking. :P