shoenig/go-mqtt

Issues

• force disconnect sends outbound message

  #27 opened 10 years ago by shoenig
  0

• websockets and ssl

  #26 opened 10 years ago by shoenig
  0

• NewClient sets sessId twice

  #25 opened 10 years ago by shoenig
  0

• No support for any sort of TLS

  #5 opened 11 years ago by shoenig
  1

• ConnRC is never checked

  #12 opened 11 years ago by robert17
  1

• sample crashes if no port specified

  #24 opened 10 years ago by shoenig
  0

• An idle client never notices server is gone

  #23 opened 11 years ago by shoenig
  2

• Error handling

  #15 opened 11 years ago by robert17
  2

• No limit on maximum number of in-flight messages

  #6 opened 11 years ago by shoenig
  1

• Concurrent calls to onPublishReceived results in appearence of out-of-order messages

  #18 opened 11 years ago by shoenig
  1

• incoming QoS 2 publishes should only be given to app if not processed

  #22 opened 11 years ago by robert17
  0

• During resume(), incoming messages can arrive before resuming from persisted state is completed

  #19 opened 11 years ago by shoenig
  1

• Receipts needs some locking

  #21 opened 11 years ago by shoenig
  0

• Memstore needs some locking

  #20 opened 11 years ago by shoenig
  0

• QoS 2 does not actually provide persistence

  #3 opened 11 years ago by shoenig
  0

• API Redesign Thoughts

  #14 opened 11 years ago by shoenig
  3

• Cleanup trace statements

  #13 opened 11 years ago by shoenig
  1

• Race Conditions detected with -race

  #17 opened 11 years ago by shoenig
  1

• Add timestamps to trace statements

  #16 opened 11 years ago by robert17
  1

• filestore should create backup file of existing message before overwriting

  #10 opened 11 years ago by shoenig
  0

• Windows filesystem trips over itself

  #11 opened 11 years ago by shoenig
  2

• Close connection on lack of PINGREQ after keepalive interval

  #8 opened 11 years ago by shoenig
  1

• Do not start keeplive goroutine if Keep Alive Timer is zero

  #9 opened 11 years ago by shoenig
  1

• Maximum message size of 1MB instead of 256MB

  #4 opened 11 years ago by shoenig
  0

• incoming messages grouped together by server are not split up

  #2 opened 11 years ago by shoenig
  0

• Modifying an opts object should not modify any client objects that were created using it

  #7 opened 11 years ago by shoenig
  1

• decode does not take into account variable length header when decoding payload

  #1 opened 11 years ago by shoenig
  1