trolly wrote:A debugger will not help here because DNS is an Operating System Service which means that the code will jump into the kernel space where you can not follow.
no. any caller of the MS api will have to set up storage per the call's spec; if the call returns, what is in that storage is clues. if the call doesn't return, that's a clue. i expect Fx then calls the error routine, which can return thousands of errors, quite specific. inspecting all this before throwing up the Not Found message is the 1st step. do you know if debug verbosity logging exists in this app?
trolly wrote:So i do not see anything where the FF devs can tune.
very incorrect. do you have experience designing network socket level apps? any programmer who claimed it was the snow and not code causing transient errors in the satellite networked clients app, would be fired.
here's a diagram for you:
1. call returns 0
-> great.
2. call call returns non-zero
-> check the RC. it could contain status that means permanent error explicitly
-> retry if non permanent error!
-> then throw a verbose, meaningful, helpful error message.
3. call never returns (user sees hang)
-> call must be set up on timer that pops after certain time if no answer
-> retry
-> throw 'no answer' verbose message
trolly wrote:You can either file a bug
not appropriate for me to do it, as it doesn't happen to me. the OP, who seemed quite savvy, is the appropriate person, but i'm sure is long gone after several pages of useless advice. frankly, a simple examination of the Fx code leading up to the throwing of the error will tell you everything you need about whether the design is solid in handling transient network exceptions.
trolly wrote:BTW: Many posters is a subjective term if compared to over 100 million downloads. I do not doubt that there is a problem but i have no idea which one.
i don't understand what this means. let me be clear on what i meant: the driveby troglodite Fx bully is just a fact of life; when mods or wannabe jr mods or anyone with an officious mozillazine tag belittle bug reporters, offer bad advice, blame it on 'windows download', refuse to file bugs, or simply have no clue about software, then that's just BS. and extremely destructive to Fx.
you have no idea (nor do i) how many people are out there, silently hitting refresh, constantly. but apparently it's enough of a problem for someone that they wrote an extension to Retry.
think i'm finished with this one..