An extra delay seems to be required between requests

[Riches]

The README tells us that "Only one request can be done at a time by each client. You'll have to wait for the first request to be processed before sending another one."

I've implemented a queue that processes the next request only after the previous one has returned its promise. However, requests seem to hang unless an additional 700ms delay is added after the GC returns and the promise is satisfied.

Is there a programmatic way to identify when the GC is ready for a new request? Or is this a bug with this implementation?

Many thanks for any assistance.

[balthazar]

Unfortunately no, or at least not to my knowledge, and that's why it's not integrated by default. Still looking for solutions atm, but you're welcome to keep me up-to-date if you find anything ;)

[Riches]

Ah right, I'll keep playing around for a bit looking around for some kind of solution. Cheers.

[Maarethyu]

I am pretty sure you can only do 1 request per second, but I don't remember where this info comes from so I may be wrong.