nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

listfolder/longpoll - timeouts on Dropbox Java SDK (v2)

Antti R.

listfolder/longpoll endpoint on Java API gets SocketTimeOut.

This is understandable, since in:

com.dropbox.core.http.HttpRequestor

You have set the connection read timeout to 20 seconds while at server side you have declared 30 secs in docs.

A dirty workaround is to subclass StandardHTTPRequestor but ideally would like to have this "just" work. Also, having different connection timeouts based on request type would not hurt...

I wonder how what kind of tests have been made on Java SDK? Anyway, if this longpoll stuff is not properly tested, what is your policy for standard polling? I already implemented and tested that for my app so would like to use that instead if longpoll is going to be fragile.

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Thanks for the report! We'll work on getting that fixed up.

As far as normal polling is concerned, we don't have any specific guidance, but there is a rate limiting system that will error out requests if you call too quickly.

Greg-DB

This should be fixed as of version 2.0-beta-6 of the SDK, where we exposed the ability to configure socket read timeouts for StandardHttpRequestor.

You can find a sample of using longpoll here:

https://github.com/dropbox/dropbox-sdk-java/blob/master/examples/longpoll/src/com/dropbox/core/examples/longpoll/Main.java