Hacker News new | past | comments | ask | show | jobs | submit login

This is great, thanks! Quick question: Is there a best practice for handling rate limiting? I.e. if you send us X number of web hook updates in quick succession for a user, are we ok just sending X delta requests back at you in quick succession? Or do we need to worry about rate limiting? What's the maximum rate we can expect to be sent web hook requests for one user?



Take a look at https://www.dropbox.com/developers/webhooks/tutorial#best-pr..., specifically the part about managing concurrency.

There are rate limits (per user) on the Dropbox side, but they're pretty high. I think the bigger concurrency issue is going to be on your end (making sure you don't process the same changes multiple times). Taking a lease per-user is a good start, and we're going to publish a more advanced sample in the coming weeks that uses a queue to really eliminate duplicate calls.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: