mosquitto/test
Roger A. Light cdbe62c2bb Outgoing messages with QoS>0 are no longer retried after a timeout.
This change in behaviour can be justified by considering when the
timeout may have occurred.

* If a connection is unreliable and has dropped, but without one end
  noticing, the messages will be retried on reconnection. Sending
  additional PUBLISH or PUBREL would not have changed anything.

* If a client is overloaded/unable to respond/has a slow connection then
  sending additional PUBLISH or PUBREL would not help the client catch
  up. Once the backlog has cleared the client will respond. If it is not
  able to catch up, sending additional duplicates would not help either.
2015-05-24 11:59:53 +01:00
..
broker Outgoing messages with QoS>0 are no longer retried after a timeout. 2015-05-24 11:59:53 +01:00
lib Outgoing messages with QoS>0 are no longer retried after a timeout. 2015-05-24 11:59:53 +01:00
ssl Add client test for encrypted x509 keys. 2014-05-26 15:48:07 +01:00
fake_user.c Initial contribution. 2014-05-07 23:27:00 +01:00
Makefile Initial contribution. 2014-05-07 23:27:00 +01:00
mosq_test.py Don't free here, leads to potential double free. 2014-07-03 17:37:31 +01:00
msgsps_common.h Initial contribution. 2014-05-07 23:27:00 +01:00
msgsps_pub.c Initial contribution. 2014-05-07 23:27:00 +01:00
msgsps_sub.c Initial contribution. 2014-05-07 23:27:00 +01:00
packet-gen.c Last raft of renames for the moment. 2015-05-18 09:29:22 +01:00
qos.c Initial contribution. 2014-05-07 23:27:00 +01:00
to-test Initial contribution. 2014-05-07 23:27:00 +01:00