search

gbishop / outfox

Automatically exported from code.google.com/p/outfox
Other
1 stars 0 forks source link

It would be nice to have some way of detecting a timeout when fetching sounds #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Maybe we should get back an error event if the sound fetch hasn't happened
after some delay. Otherwise it is difficult to know when to proceed. 

I guess I could do it myself with a timer and issue a stop to cancel the
outstanding stuff?

Original issue reported on code.google.com by piisnear...@gmail.com on 13 Sep 2008 at 8:07

GoogleCodeExporter commented 9 years ago 
The timeout code should live in the cache.js file where the xhr is initiated. 
Should
the timeout value be part of the JSON command? (I believe yes.) Should time be
absolute or time since the last progress notification from the request (e.g., it
doesn't finishing in 5 seconds versus it hasn't progressed in the last 5 
seconds)? (I
think the latter).

Original comment by c...@unc.edu on 18 Sep 2008 at 1:40

GoogleCodeExporter commented 9 years ago 
Believe this was fixed when error reporting for bad sound URLs landed. Sooner 
or later the request will timeout and an error will be reported back to the 
client. Not sure if there's a way to control the timeout duration. Will leave 
this bug open while researching that.

Original comment by c...@unc.edu on 13 Dec 2008 at 1:09

GoogleCodeExporter commented 9 years ago 
Marking closed for now. Reopen if problem still exists.

Original comment by c...@unc.edu on 24 Jan 2009 at 4:25