Is Google's Webspeech server request-limiting me, and is there a fix?
I've been writing an extension that allows the user to issue voice
commands to control their browser, and things were going great until I hit
a catastrophic problem. It goes like this:
The speech recognition object is in continuous mode, and whenever the
onerror: 'no-speech' or onend events fire, it restarts. This way, the
extension is constantly waiting to accept input and reacts whenever a
command is issued, even after 5 minutes of silence.
After a few days of of development, today I reached the point where I was
testing it in practical use, and I found that after a little while (and
with no change to anything on my part), my onend event started firing
constantly. As in, looking at the console, I would see 18,000 requests
being made in the space of three seconds, all being instantly denied, thus
triggering onend and restarting the request.
I'm aware that it would be optimal to wait for sound before sending a
request, or to have local speech recognition capabilities without the need
for a remote server, but the present API does not allow that.
Are my suspicions correct? Am I getting request limited?
No comments:
Post a Comment