Forum Discussion
2 Replies
- AdamN13 years agoKhoros Oracle
By default, the session will time out after 30 minutes of inactivity and will max out at 24 hours. I don't believe there is a hard limit on how many REST API sessions a single user can have, though it would be a good idea to refer to the "Throttling" portion of the REST API JavaDocs if you are planning to make frequent requests or require a large number of sessions.
In the index.html of the javadoc i have found :
Throttling The API does not currently throttle the speed or number of requests. However, clients of the API should still be aware of standard HTTP protocol responses and act accordingly. For instance, the client should detect the 503 (server too busy) status code to slow down, and follow redirections (302) appropriately.
It's very interesting, i will take care of this 2 errors code.I have noticed the 301 error code when the session key is not valid. There is another example where the 301 error code is returned ?
There is a document about all error code?
503 : the server is too busy, a server can be slow but not others, we need to recall the url without pause ?
302 : you have an example of the lithium response ?
Thanks
Sylvain
Related Content
- 5 years ago