You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to specify quotaUser upon Speech Streaming request #475
So far I cannot find out how to do that from Cloud Speech API doc.
Could you please help me providing a sample code in python?
if it even better if you use speech_streaming.py example code.
@heroddaji Support for the quotaUser is no longer available. If the request is authenticated, the user QPS limit applies to the actual user (Google user ID). Otherwise, client IP is used. Hope that helps.
@heroddaji Can you please give me details and specifics about how you are using or intend to use the speech api and distribute it to your users? I do get a sense from your previous comment, but I don't want to assume. Thanks.
@heroddaji you shouldn't distribute your service account private key to end users. Client applications can't keep secrets, and private keys are intended for server-to-server communication.
@heroddaji Closing this due to no activity. Please, open another issue if you have further questions. Also, adding to what @jonparrott said you should architect your system such that your app talks to the service which behind the scenes invokes the Speech API using the service account.
Activity
puneith commentedon Aug 24, 2016
@heroddaji Please take a loot at https://cloud.google.com/speech/limits to use the API appropriately.
theacodes commentedon Aug 24, 2016
@heroddaji it doesn't appear our grpc clients currently expose the ability to do userquota, or if they do, it's very non-obvious how to do so.
theacodes commentedon Aug 24, 2016
@heroddaji there are several ways to limit it from your end (such as with redis).
puneith commentedon Aug 25, 2016
@heroddaji Support for the quotaUser is no longer available. If the request is authenticated, the user QPS limit applies to the actual user (Google user ID). Otherwise, client IP is used. Hope that helps.
heroddaji commentedon Aug 25, 2016
thank you, i have not yet fully understand the part "the user QPS limit applies to the actual user (Google user ID)".
In which situation this applies? because in our app, we will use our google_json_secret key (our id). and distribute the app to users:
Sorry for confusion, but I hope you all can help me.
puneith commentedon Aug 25, 2016
@heroddaji Can you please give me details and specifics about how you are using or intend to use the speech api and distribute it to your users? I do get a sense from your previous comment, but I don't want to assume. Thanks.
theacodes commentedon Aug 25, 2016
@heroddaji you shouldn't distribute your service account private key to end users. Client applications can't keep secrets, and private keys are intended for server-to-server communication.
puneith commentedon Sep 16, 2016
@heroddaji Closing this due to no activity. Please, open another issue if you have further questions. Also, adding to what @jonparrott said you should architect your system such that your app talks to the service which behind the scenes invokes the Speech API using the service account.
chore(python): add support for python 3.11 (#475)
chore(main): release 3.11.0 (#475)
chore(python): add support for python 3.11 (#475)
chore(python): add support for python 3.11 (#475)
chore(deps): update all dependencies (#475)
chore: migrate code from googleapis/python-datastore (#13837)