adding retries and timeout-parameters to all levels of the software-stack
pushing timeout/retries from top to bottom
executing retry-loop only from at_response
The number of retries can now be controlled at application-level, the user of the library can decide if she needs many retries or prefers fast failing.
The patches also gets rid of a number of loops that either never did what they should do or which were never executed anyhow.
This patch fixes #61 by
at_responseThe number of retries can now be controlled at application-level, the user of the library can decide if she needs many retries or prefers fast failing.
The patches also gets rid of a number of loops that either never did what they should do or which were never executed anyhow.