shoenig go-mqtt issues - Githubissues

shoenig / go-mqtt

A development fork of the Eclipse Paho Go MQTT client

http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.golang.git/

Eclipse Public License 1.0

13 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

force disconnect sends outbound message

#27 shoenig opened 10 years ago
0
websockets and ssl

#26 shoenig opened 10 years ago
0
NewClient sets sessId twice

#25 shoenig opened 10 years ago
0
sample crashes if no port specified

#24 shoenig opened 10 years ago
0
An idle client never notices server is gone

#23 shoenig opened 10 years ago
2
incoming QoS 2 publishes should only be given to app if not processed

#22 robert17 opened 10 years ago
0
Receipts needs some locking

#21 shoenig closed 10 years ago
0
Memstore needs some locking

#20 shoenig closed 10 years ago
0
During resume(), incoming messages can arrive before resuming from persisted state is completed

#19 shoenig closed 10 years ago
1
Concurrent calls to onPublishReceived results in appearence of out-of-order messages

#18 shoenig closed 10 years ago
1
Race Conditions detected with -race

#17 shoenig closed 10 years ago
1
Add timestamps to trace statements

#16 robert17 closed 10 years ago
1
Error handling

#15 robert17 closed 10 years ago
2
API Redesign Thoughts

#14 shoenig closed 10 years ago
3
Cleanup trace statements

#13 shoenig closed 10 years ago
1
ConnRC is never checked

#12 robert17 closed 10 years ago
1
Windows filesystem trips over itself

#11 shoenig closed 10 years ago
2
filestore should create backup file of existing message before overwriting

#10 shoenig closed 10 years ago
0
Do not start keeplive goroutine if Keep Alive Timer is zero

#9 shoenig closed 10 years ago
1
Close connection on lack of PINGREQ after keepalive interval

#8 shoenig closed 10 years ago
1
Modifying an opts object should not modify any client objects that were created using it

#7 shoenig closed 10 years ago
1
No limit on maximum number of in-flight messages

#6 shoenig closed 10 years ago
1
No support for any sort of TLS

#5 shoenig closed 10 years ago
1
Maximum message size of 1MB instead of 256MB

#4 shoenig closed 10 years ago
0
QoS 2 does not actually provide persistence

#3 shoenig closed 10 years ago
0
incoming messages grouped together by server are not split up

#2 shoenig closed 10 years ago
0
decode does not take into account variable length header when decoding payload

#1 shoenig closed 10 years ago
1