Board Thread:JS Development/@comment-9605025-20191030060753/@comment-9605025-20191207201455

I see. But what is the purpose of depreciating synchronous requests if all that does is force certain use cases to coerce asynchronous requests into synchronous requests anyways? Is there some benefit to sing synchronous asynchronous requests over synchronous requests?

Also, I am still unclear on how serializing the requests (regardless of how many queues you have going) actually helps with the rate issue. Say the rate limit is the same as editing (1 per second) and each request takes, say 20 ms. Then, even if I serialize them, that is 50 requests per second; way more than the limit. Or is the logic behind serializing that the server can set the limit by controlling how frequently is sends the replies?