Good point: keeping more out of the library. Then the library and client complexity do not to stack together. No "do the stuff" function that manages everything. :)

The queue can also be managed by the client. As an example, you might want to use the lib to try to overflow another implementation to test the request load it can handle.

Are the request also non-blocking if the client is not connected to internet anymore (and unable to receive packet at all)?