| Commit message (Collapse) | Author | Age | Lines | |
|---|---|---|---|---|
| * | facebook-mqtt: propagate actual connection error code | jgeboski | 2015-01-23 | -2/+1 |
| | | | | | | | As of now, the connection error code is only a general error code. It should be the actual error code retrieved from the MQTT service. This was an oversight when implementing the original MQTT interface. | |||
| * | facebook-mqtt: reset the connected state upon closing | jgeboski | 2015-01-23 | -0/+2 |
| | | | | | | The connected state should be reset when the connection is closed. This was an oversight when implementing the original MQTT interface. | |||
| * | facebook-mqtt: fixed preemptive connection timeouts | jgeboski | 2015-01-17 | -2/+2 |
| | | | | | | | | | | As it stands, a connection is declared as being timed out if it has not heard back from the server with a ping response in one keep-alive time interval. However, the MQTT specification states that a connection is only declared timed out after one and a half time intervals. While the effects of this oversight may not be immediately present, over a period uptime, the connection may fall victim to preemptive timeouts. | |||
| * | Implemented initial MQTT interface | jgeboski | 2015-01-14 | -0/+1057 |
 |
index : bitlbee-facebook | |
| github.com/jgeboski/bitlbee-facebook with some local patches | Marius Halden |
| aboutsummaryrefslogtreecommitdiffstats |