In doReadTransferAsync() currently a new TransferFuture and notification queue is created. This involves dynamic memory allocation and should be avoided. Instead the TransferFuture should be stored in the first call (or even in the constructor) and reused in any subsequent calls.
In doReadTransferAsync() currently a new TransferFuture and notification queue is created. This involves dynamic memory allocation and should be avoided. Instead the TransferFuture should be stored in the first call (or even in the constructor) and reused in any subsequent calls.