As discovered by @SimonErm in #104, the socket write timeout is fairly low (especially assuming this client can be used on lower quality mobile networks) and hardcoded.
Neither should be the case. The timeout of 55 seconds (a bit lower than the default RabbitMQ heartbeat timeout of 60) seems like a good conservative option to me but above all it should be a configurable setting.
As discovered by @SimonErm in #104, the socket write timeout is fairly low (especially assuming this client can be used on lower quality mobile networks) and hardcoded.
Neither should be the case. The timeout of 55 seconds (a bit lower than the default RabbitMQ heartbeat timeout of 60) seems like a good conservative option to me but above all it should be a configurable setting.