Is there a limit on api automated queries where user will try to flood the system?
I believe what you're looking for is App Throttling - Configuration and Mechanics. Default is to warn at 70, fail at 150 within a 10 second period. This can also be customized via System Property jive.api.throttle.definition.app.
Why can't users add comments to the App Throttling - Configuration and Mechanics document? GaryAJ
Having a property value of "Limit to: 70 (150!) per 10s" is very advanced, but one may wonder whether the needed AI is implemented to understand also mal-formed values (typos). It may be more admin-friendly to have three values: jive.api.throttle.definition.app.warning=70, .fail=150 and .interval=10.
Comments have been disabled for that document. As to the reasoning behind the required formatting of jive.api.throttle.definition.app, I really couldn't tell you. My experience with these system properties is that there is typically 0 wiggle room for the allowed or functioning values. It wouldn't be a bad idea to simplify the required values by segmenting the property iinto a .warning, .fail and .interval. I might suggest throwing it out there as an Idea within our Jive Interactive Intranet Space.
I expect less than five votes to improve a system property which has now a rather uncommon value - so I will not create an idea. The worst thing about ideas is that one does usually not get any feedback by Jive, a brick in the wall is more communicative. Please do not tell me to create an idea that you review and rate all ideas which are older than 12 months.
PS: Some companies are able to create an internal (Jira) issue without much overhead and simply fix obvious things.
[Commenting on Docs]
There are actually two reasons that comments are turned off. The first is that when we migrated from the old developer community, we thought we might actually move the docs to the main landing page and make them simply be regular web pages. If we did that, we didn't want to lose the comments--which are often very valuable. The second reason was that in the previous community, because documentation was in a different space, the conversations got fragmented. So we thought it would be good to have one clean set of docs and just let the conversations occur here. This is pretty easy now that everything is together.
Now the doc is here, but one can still not comment. Also within the "official" documentaion (docs.jivesoftware.com) it would be nice to be able to comment (similar to PHP: printf - Manual) - with Jive Anywhere this is somehow possible.
Retrieving data ...